Summary: | gcc-4.1.2 fails to compile in insn-attrtab.o | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tom Lloyd <napalmllama> |
Component: | [OLD] GCC Porting | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | truedfx |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tom Lloyd
2008-04-22 16:55:45 UTC
This is almost certainly because you don't have enough memory; GCC needs a lot at this point. You should have more success with MAKEOPTS=-j1, or with more swap space added. If you still hit errors afterwards that look similar to this, please reopen this bug. *** This bug has been marked as a duplicate of bug 151023 *** It must be some phenomenal memory-muncher then - I have gig of RAM and another gig of swap! OK, I'm fairly certain that it isn't an out-of-memory issue. I just upped the swap to 2Gb, and set MAKEOPTS="-j1", as you suggested, and the build still fails in the same place. I got slightly different output this time because the kernel didn't trip up as before: stage1/xgcc -Bstage1/ -B/usr/x86_64-pc-linux-gnu/bin/ -march=athlon64 -O2 -pipe -fprofile-generate -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/sys-devel/gcc-4.1.2/work/gcc-4.1.2/gcc -I/var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/gcc/. -I/var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/gcc/../include -I/var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/gcc/../libcpp/include -c insn-attrtab.c \ -o insn-attrtab.o /var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/gcc/config/i386/i386.md: In function 'internal_dfa_insn_code': /var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/gcc/config/i386/i386.md:200: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. The bug is not reproducible, so it is likely a hardware or OS problem. make[2]: *** [insn-attrtab.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/gcc' make[1]: *** [stageprofile_build] Error 2 make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/gcc' make: *** [profiledbootstrap] Error 2 ...and the reason I'm /sure/ it wasn't an out-of-memory error? I ran the following while I was compiling: $ while [ ! -z `pgrep emerge` ] > do date > free > echo > sleep 5 > done The last dozen or so entries (I didn't have any scrollback) all show almost zero swap usage and about 500Mb free -/+ buffers/cache. If it's any help, this is a fresh install using a 2008.0_beta1 stage3 tarball. I cross-compiled the kernel from my 32bit install, (so I didn't have to download and boot the ISO), but that's the only oddity about the whole setup. Re-opening... ...so that the toolchain folks can take a look at this new error message. :) this line is pretty significant: The bug is not reproducible, so it is likely a hardware or OS problem. that means the gcc code re-ran the code that segfaulted and it didnt segfault the second time ... *** This bug has been marked as a duplicate of bug 20600 *** Well then maybe this is a bug for the releng team? I'm sorry to keep bothering you, but like I said this is a fresh install of 2008.0_beta1. If the standard release being put out by Gentoo is failing on a pretty standard AMD64 rig, there's got to be a problem somewhere. My hardware is solid; I've never had any problems with it in 3 years. it's a resource issue. gcc-4.1.2 is known to consume memory when building. in fact, the error message you posted originally indicated this: ...splig kernel: Bad pagetable: 000f [1] PREEMPT... that means you ran out of resources and the kernel killed it you can remove -pipe from CFLAGS while building gcc and that may also help |