http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48835



--- Comment #54 from Mikael Pettersson <mikpe at it dot uu.se> 2013-03-20 
11:05:58 UTC ---

Status update:



Although gnat is solid enough to rebuild itself with (patched) gcc-4.6 on m68k,

there is a regression with (similarly patched) 4.7 that breaks bootstrap:



/mnt/scratch/objdir47/./gcc/xgcc -B/mnt/scratch/objdir47/./gcc/

-B/usr/m68k-brewer-linux/bin/ -B/usr/m68k-brewer-linux/lib/ -isystem

/usr/m68k-brewer-linux/include -isystem /usr/m68k-brewer-linux/sys-include   

-c -g -O2 -mcpu=68060 -fpic  -W -Wall -gnatpg -nostdinc -mcpu=68060 

a-calfor.adb -o a-calfor.o

xgcc: internal compiler error: Segmentation fault (program gnat1)

Please submit a full bug report,

with preprocessed source if appropriate.

make[9]: *** [a-calfor.o] Error 4

make[9]: Leaving directory `/mnt/scratch/objdir47/gcc/ada/rts_m68060'

make[8]: *** [gnatlib] Error 2

make[8]: Leaving directory `/mnt/scratch/objdir47/gcc/ada'

make[7]: *** [gnatlib-shared-default] Error 2

make[7]: Leaving directory `/mnt/scratch/objdir47/gcc/ada'

make[6]: *** [gnatlib-shared-dual] Error 2

make[6]: Leaving directory `/mnt/scratch/objdir47/gcc/ada'

make[5]: *** [gnatlib-shared] Error 2

make[5]: Leaving directory `/mnt/scratch/objdir47/gcc/ada'

make[4]: *** [gnatlib-shared] Error 2

make[4]: Leaving directory

`/mnt/scratch/objdir47/m68k-brewer-linux/m68060/libada'

make[3]: *** [multi-do] Error 1

make[3]: Leaving directory `/mnt/scratch/objdir47/m68k-brewer-linux/libada'

make[2]: *** [all] Error 2

make[2]: Leaving directory `/mnt/scratch/objdir47/m68k-brewer-linux/libada'

make[1]: *** [all-target-libada] Error 2

make[1]: Leaving directory `/mnt/scratch/objdir47'

make: *** [bootstrap] Error 2



This only occurs when compiling the 68060 variant of the libraries.  With

multilibs disabled 4.7.3 bootstraps fine w/ Ada.



This ICE started with r180192, an ICE fix (PR50780).  I don't see anything in

that patch that seems m68k or cc0 related, so I suspect it just exposed some

latent issue.

Reply via email to