Gerald Pfeifer <ger...@pfeifer.com> writes: > On Tue, 2 Sep 2014, Richard Sandiford wrote: >> Also, i386 was robust against uses of %& in inline asm. The patch >> makes sure the other ports are too. Using %& in inline asm would >> often be a mistake, but it should at least trigger a proper error >> rather than an ICE. >> >> Tested on x86_64-linux-gnu. Also tested by building cross compilers >> before and after the change on: >> >> alpha-linux-gnu powerpc64-linux-gnu s390x-linux-gnu sparc64-linux-gnu > > Is it possible this is related to the following new (set of) bootstrap > failure(s) my i386-unknown-freebsd10.0 tester shows as new in the last > 24 hours? > > /scratch2/tmp/gerald/gcc-HEAD/libgcc/libgcc2.c: In function '__lshrdi3': > /scratch2/tmp/gerald/gcc-HEAD/libgcc/libgcc2.c:426:1: internal compiler > error: in gen_variable_die, at dwarf2out.c:19017 > } > ^ > /scratch2/tmp/gerald/gcc-HEAD/libgcc/libgcc2.c: In function '__ashrdi3': > /scratch2/tmp/gerald/gcc-HEAD/libgcc/libgcc2.c: In function '__ashldi3': > /scratch2/tmp/gerald/gcc-HEAD/libgcc/libgcc2.c:483:1: internal compiler > error: in gen_variable_die, at dwarf2out.c:19017 > } > ^ > /scratch2/tmp/gerald/gcc-HEAD/libgcc/libgcc2.c:454:1: internal compiler > error: in gen_variable_die, at dwarf2out.c:19017 > } > ^ > > Parallel build, hence three ICEs at once. :-)
Is this stage 1 libgcc or a later libgcc? Seems unlikely if stage 1. Thanks, Richard
