http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54705
--- Comment #2 from mikulas at artax dot karlin.mff.cuni.cz 2012-09-26 23:12:18
UTC ---
My script doesn't have -g, but it is somehow added by gcc build scripts. I can
see lines like this that have -g.
/usr/src/gcc-4.7.2-build-5.1/./prev-gcc/xgcc
-B/usr/src/gcc-4.7.2-build-5.1/./prev-gcc/
-B/usr/local/gcc/x86_64-unknown-linux-gnu/bin/
-B/usr/local/gcc/x86_64-unknown-linux-gnu/bin/
-B/usr/local/gcc/x86_64-unknown-linux-gnu/lib/ -isystem
/usr/local/gcc/x86_64-unknown-linux-gnu/include -isystem
/usr/local/gcc/x86_64-unknown-linux-gnu/sys-include -c -O3 -march=barcelona
-fomit-frame-pointer -flto -gtoggle -gnatpg -gnata -W -Wall -g -O1 -fno-inline
\
-nostdinc -I- -I. -Iada -I../../gcc-4.7.2/gcc/ada
-I../../gcc-4.7.2/gcc/ada/gcc-interface ../../gcc-4.7.2/gcc/ada/a-except.adb -o
ada/a-except.o
For me it is reproducible, I ran it again and it crashed again with the same
internal error. I am attaching the output of the compilation so that you can
look where the -g came from.
