Error during make bootstrap (on Mandrake 10) with latest CVS. ../gcc/configure --enable-threads=posix --prefix=/home/jmv/usr2/gcc \ --enable-shared --enable-languages=c++,java \ --with-x --enable-gtk-cairo \ --enable-java-awt=gtk --enable-version-specific-runtime-libs .... time make bootstrap .... ar rc ./libgcc.a libgcc/./_muldi3.oS libgcc/./_negdi2.oS libgcc/./_lshrdi3.oS libgcc/./_ashldi3.oS libgcc/./_ashrdi3.oS libgcc/./_cmpdi2.oS libgcc/./_ucmpdi2.oS libgcc/./_floatdidf.oS libgcc/./_floatdisf.oS libgcc/./_fixunsdfsi.oS libgcc/./_fixunssfsi.oS libgcc/./_fixunsdfdi.oS libgcc/./_fixdfdi.oS libgcc/./_fixunssfdi.oS libgcc/./_fixsfdi.oS libgcc/./_fixxfdi.oS libgcc/./_fixunsxfdi.oS libgcc/./_floatdixf.oS libgcc/./_fixunsxfsi.oS libgcc/./_fixtfdi.oS libgcc/./_fixunstfdi.oS libgcc/./_floatditf.oS libgcc/./_clear_cache.oS libgcc/./_enable_execute_stack.oS libgcc/./_trampoline.oS libgcc/./__main.oS libgcc/./_absvsi2.oS libgcc/./_absvdi2.oS libgcc/./_addvsi3.oS libgcc/./_addvdi3.oS libgcc/./_subvsi3.oS libgcc/./_subvdi3.oS libgcc/./_mulvsi3.oS libgcc/./_mulvdi3.oS libgcc/./_negvsi2.oS libgcc/./_negvdi2.oS libgcc/./_ctors.oS libgcc/./_ffssi2.oS libgcc/./_ffsdi2.oS libgcc/./_clz.oS libgcc/./_clzsi2.oS libgcc/./_clzdi2.oS libgcc/./_ctzsi2.oS libgcc/./_ctzdi2.oS libgcc/./_popcount_tab.oS libgcc/./_popcountsi2.oS libgcc/./_popcountdi2.oS libgcc/./_paritysi2.oS libgcc/./_paritydi2.oS libgcc/./_divdi3.oS libgcc/./_moddi3.oS libgcc/./_udivdi3.oS libgcc/./_umoddi3.oS libgcc/./_udiv_w_sdiv.oS libgcc/./_udivmoddi4.oS libgcc/./_eprintf.oS libgcc/./__gcc_bcmp.oS ranlib ./libgcc.a ./xgcc -B./ -B/home/jmv/usr2/gcc/i686-pc-linux-gnu/bin/ -isystem /home/jmv/usr2/gcc/i686-pc-linux-gnu/include -isystem /home/jmv/usr2/gcc/i686-pc-linux-gnu/sys-include -L/usr/src/gcc-cvs/objdir/gcc/../ld -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include -I../../gcc/gcc/../libbanshee/libcompat -I../../gcc/gcc/../libbanshee -I../../gcc/gcc/../libbanshee/points-to -DL_gcov -c ../../gcc/gcc/libgcov.c -o libgcc/./_gcov.o ./xgcc -B./ -B/home/jmv/usr2/gcc/i686-pc-linux-gnu/bin/ -isystem /home/jmv/usr2/gcc/i686-pc-linux-gnu/include -isystem /home/jmv/usr2/gcc/i686-pc-linux-gnu/sys-include -L/usr/src/gcc-cvs/objdir/gcc/../ld -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include -I../../gcc/gcc/../libbanshee/libcompat -I../../gcc/gcc/../libbanshee -I../../gcc/gcc/../libbanshee/points-to -DL_gcov_merge_add -c ../../gcc/gcc/libgcov.c -o libgcc/./_gcov_merge_add.o ../../gcc/gcc/libgcov.c:503: internal compiler error: in pop_scope, at c-decl.c:797 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. make[3]: *** [libgcc/./_gcov_merge_add.o] Erreur 1 make[3]: Leaving directory `/usr/src/gcc-cvs/objdir/gcc' make[2]: *** [libgcc.a] Erreur 2 make[2]: Leaving directory `/usr/src/gcc-cvs/objdir/gcc' make[1]: *** [stage2_build] Erreur 2 make[1]: Leaving directory `/usr/src/gcc-cvs/objdir/gcc' make: *** [bootstrap-lean] Erreur 2 make bootstrap-lean 2464,12s user 97,88s system 72% cpu 58:57,12 total
hmm, it worked for me.
Subject: Re: internal compiler error in pop_scope pinskia at gcc dot gnu dot org wrote: >------- Additional Comments From pinskia at gcc dot gnu dot org 2004-08-20 08:02 ------- >hmm, it worked for me. > > What can we do ? What can I check ? In fact I never could complete a compilation from the CVS, although I tried many times during last months.
What it sounds like is that stage1 is being miscompiled by the compiler you are using. Can you try to bootstrap with a different compiler first.
Subject: Re: internal compiler error in pop_scope pinskia at gcc dot gnu dot org wrote: >------- Additional Comments From pinskia at gcc dot gnu dot org 2004-08-20 09:06 ------- >What it sounds like is that stage1 is being miscompiled by the compiler you are using. > >Can you try to bootstrap with a different compiler first. > > Thanks. OK, my gcc 3.3 was probably broken. So I updated : gcc, binutils, glibc-devel But now I have an unstable Mandrake cooker version :-(( gcc --version gcc (GCC) 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk) I should probably download a stable binary.
Subject: Re: internal compiler error in pop_scope pinskia at gcc dot gnu dot org wrote: >------- Additional Comments From pinskia at gcc dot gnu dot org 2004-08-20 09:06 ------- >What it sounds like is that stage1 is being miscompiled by the compiler you are using. > >Can you try to bootstrap with a different compiler first. > > > Now I get to stage 2 ! Please could you again give me some hint ? make bootstrap ... Automaton `athlon_fp' 15522 NDFA states, 99908 NDFA arcs 15522 DFA states, 99908 DFA arcs 463 minimal DFA states, 3038 minimal DFA arcs 273 all insns 21 insn equivalence classes 3057 transition comb vector els, 9723 trans table els: use comb vect 3057 state alts comb vector els, 9723 state alts table els: use comb vect 9723 min delay table els, compression factor 1 17533 all allocated states, 102661 all allocated arcs 32710 all allocated alternative states 6256 all transition comb vector els, 16780 all trans table els 6256 all state alts comb vector els, 16780 all state alts table els 16780 all min delay table els 0 locked states num transformation: 0.015998, building DFA: 7.881801 DFA minimization: 0.649902, making insn equivalence: 0.002999 all automaton generation: 9.000632, output: 0.187972 /bin/sh ../../gcc/gcc/../move-if-change tmp-attrtab.c insn-attrtab.c echo timestamp > s-attrtab stage2/xgcc -Bstage2/ -B/home/jmv/usr2/gcc/i686-pc-linux-gnu/bin/ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Werror -fno-common -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include -I../../gcc/gcc/../libbanshee/libcompat -I../../gcc/gcc/../libbanshee -I../../gcc/gcc/../libbanshee/points-to -c insn-attrtab.c \ -o insn-attrtab.o insn-attrtab.c: In function `internal_dfa_insn_code': insn-attrtab.c:18771: error: dominator of 2911 should be 2895, not 2907 insn-attrtab.c:18771: internal compiler error: in verify_dominators, at dominance.c:842 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. make[2]: *** [insn-attrtab.o] Erreur 1 make[2]: Leaving directory `/usr/src/gcc-cvs/objdir/gcc' make[1]: *** [stage3_build] Erreur 2 make[1]: Leaving directory `/usr/src/gcc-cvs/objdir/gcc' make: *** [bootstrap] Erreur 2
I might go out on a limb and say that you have some hardware problems.
Subject: Re: internal compiler error in pop_scope pinskia at gcc dot gnu dot org wrote: >------- Additional Comments From pinskia at gcc dot gnu dot org 2004-08-20 15:37 ------- >I might go out on a limb and say that you have some hardware problems. > > Are you joking at me ? I used the laptop for 2 or 3 months, it's true that I had some freezes, but I thought it was due to instable Mandrake 10. Seriouly, how can I check my hardware ? This week-end , I'll test thez bootstrap with Fedora Core 2 and let you know. Jean-Marc
Subject: Re: internal compiler error in pop_scope jmvanel at free dot fr wrote: >>------- Additional Comments From pinskia at gcc dot gnu dot org 2004-08-20 15:37 ------- >>I might go out on a limb and say that you have some hardware problems. > Seriouly, how can I check my hardware ? The key thing to check is whether the bugs are reproducible. If you type "make bootstrap" 3 times in a row, do you get the exact same failure every time? You don't have to do builds from scratch. You can just try to continue builds from where they failed. If you get the same failure every time, then this is likely a gcc bug. If you get a different failure every time, then it is likely that this is either a kernel bug, or a hardware problem. If you are having sporadic kernel/hardware failures, then you may be able to complete a build if you just keep typing "make bootstrap" enough times. This probably isn't the right group to ask about detecting hardware problems. Maybe there is a linux FAQ about this somewhere? I don't know if there are free programs for this. There are probably commercial Windows based products for PCs. The BIOS might have some memory testing stuff. Trying a stable linux kernel is probably an easier and cheaper and safer solution than messing with hardware, so I'd suggest doing that first.
This works for me and many other people so closing as worksforme.