| Summary: | sys-devel/gcc-4.1.1 failed w/ ICE | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | bazancik |
| Component: | [OLD] Core system | Assignee: | PPC Porters <ppc> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | toolchain |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | PPC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
bazancik
2006-10-03 05:37:06 UTC
and if you re-emerge it, does it fail in the same place every time ? *** Bug 149956 has been marked as a duplicate of this bug. *** I re-emerged it (emerge --resume) and 29 of 224 items compiled succesfully but 30th item failed which again was gcc-4.1.1
It's 4th time it failed on ggc :(
(...)
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/reload.c: In function 'refers_to_regno_for_reload_p':
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/reload.c:6376: error: unrecognizable insn:
(insn 18 16 19 2 (set (reg/f:SI 153)
(subreg/s/u:QI (reg:SI 127 [ D.32768 ]) 3)) -1 (nil)
(nil))
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/reload.c:6376: internal compiler error: in extract_insn, at recog.c:2084
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugs.gentoo.org/> for instructions.
stage2/xgcc -Bstage2/ -B/usr/powerpc-unknown-linux-gnu/bin/ -c -O2 -pipe -mcpu=7400 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc -I/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/. -I/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/../include -I/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/../libcpp/include /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/reorg.c -o reorg.o
stage2/xgcc -Bstage2/ -B/usr/powerpc-unknown-linux-gnu/bin/ -c -O2 -pipe -mcpu=7400 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc -I/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/. -I/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/../include -I/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/../libcpp/include /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/resource.c -o resource.o
The bug is not reproducible, so it is likely a hardware or OS problem.
make[2]: *** [reload.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build/gcc'
make[1]: *** [stage3_build] Error 2
make[1]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build/gcc'
make: *** [bootstrap-lean] Error 2
!!! ERROR: sys-devel/gcc-4.1.1 failed.
Call stack:
ebuild.sh, line 1546: Called dyn_compile
ebuild.sh, line 937: Called src_compile
ebuild.sh, line 1255: Called toolchain_src_compile
toolchain.eclass, line 24: Called gcc_src_compile
toolchain.eclass, line 1534: Called gcc_do_make
toolchain.eclass, line 1408: Called die
!!! emake failed with bootstrap-lean
!!! If you need support, post the topmost build error, and the call stack if relevant.
yes, but it isnt the same file and if you read the error message: The bug is not reproducible, so it is likely a hardware or OS problem. (In reply to comment #4) > yes, but it isnt the same file and if you read the error message: > The bug is not reproducible, so it is likely a hardware or OS problem. I don't think it's a hardware problem. Every other compilation goes fine but gcc 4.1.1 always fails. Always in different place - that's a fact. Maybe problem lays somewhere else, not GCC itself. I'll keep trying to compile it... I'm using 2 different OS on my Pegasos (Debian, MorphOS) and I have no such problems on them, so hardware problem is very unlikely. -- Best regards anyway!! |
