While emerging gcc-4.1.0_beta20050618, I obtained the following stage1/xgcc -Bstage1/ -B/usr/i386-pc-linux-gnu/bin/ -c -O2 -mtune=i686 -fprofi le-generate -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-pr ototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -DHAVE_CONFIG_H -I. -I. -I/var/tmp/portage/gcc-4.1.0_beta20050618/work/gcc- 4.1-20050618/gcc -I/var/tmp/portage/gcc-4.1.0_beta20050618/work/gcc-4.1-20050618 /gcc/. -I/var/tmp/portage/gcc-4.1.0_beta20050618/work/gcc-4.1-20050618/gcc/../in clude -I/var/tmp/portage/gcc-4.1.0_beta20050618/work/gcc-4.1-20050618/gcc/../lib cpp/include /var/tmp/portage/gcc-4.1.0_beta20050618/work/gcc-4.1-20050618/gcc/s implify-rtx.c -o simplify-rtx.o /var/tmp/portage/gcc-4.1.0_beta20050618/work/gcc-4.1-20050618/gcc/simplify-rtx.c : In function simplify_const_binary_operation: /var/tmp/portage/gcc-4.1.0_beta20050618/work/gcc-4.1-20050618/gcc/simplify-rtx.c :2073: internal compiler error: in tree_verify_flow_info, at tree-cfg.c:3716 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. make[2]: *** [simplify-rtx.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/gcc-4.1.0_beta20050618/work/build/g cc' make[1]: *** [stageprofile_build] Error 2 make[1]: Leaving directory `/var/tmp/portage/gcc-4.1.0_beta20050618/work/build/g cc' make: *** [profiledbootstrap] Error 2 Reproducible: Always Steps to Reproduce: Here is the USE flags I have set : (-altivec) -bootstrap -build -debug +fortran -gcj +gtk -hardened -ip28 (-multilib) -multislot (-n32) (-n64) +nls -nocxx -objc -static I have compiled gcc4.1.0_beta20050611 without any problems.
Created attachment 61623 [details] emerge info Here comes my emerge info if you need it.
We are not supporting gcc-4 yet. Please report all bugs upstream. Make sure to provide them with the preprocessed output.
Ok (but then, you should change, if that is possible, the line "Please bug report" with a link pointing here). Anyway, I eventually found a bug similar to mine, which was solved including this patch : http://gcc.gnu.org/ml/gcc-patches/2005-06/msg01649.html