GCC build failure, HEAD@159108 on native

regress regress@apple.com
Thu May 6 14:38:00 GMT 2010


With your recent patch, GCC HEAD revision 159108 had problems on:
native: build (about the same as the previous build)
Attached is build output for those targets.
The previous build was of revision 159107.

Log information for changes since the last build:
------------------------------------------------------------------------
r159108 | hubicka | 2010-05-06 07:15:22 -0700 (Thu, 06 May 2010) | 6 lines
Changed paths:
   M /trunk/gcc/ChangeLog
   M /trunk/gcc/ipa-inline.c
   M /trunk/gcc/testsuite/ChangeLog
   A /trunk/gcc/testsuite/gcc.c-torture/compile/pr43791.c

	PR tree-optimization/43791
	* ipa-inline.c (update_caller_keys): Remove bogus
	disregard_inline_limits check.

	* gcc.c-torture/compile/pr43791.c: New file.

------------------------------------------------------------------------

For more information, see <http://gcc.gnu.org/regtest/HEAD/>.

-------------- next part --------------
ranlib: file: ../../.././gcc/ppc64/libgcc.a(_mulxc3.o) has no symbols
ranlib: file: ../../.././gcc/ppc64/libgcc.a(_divxc3.o) has no symbols
ranlib: file: ../../.././gcc/ppc64/libgcc.a(_fixunsxfsi.o) has no symbols
ranlib: file: ../../.././gcc/ppc64/libgcc.a(_fixxfdi.o) has no symbols
ranlib: file: ../../.././gcc/ppc64/libgcc.a(_fixunsxfdi.o) has no symbols
ranlib: file: ../../.././gcc/ppc64/libgcc.a(_floatdixf.o) has no symbols
ranlib: file: ../../.././gcc/ppc64/libgcc.a(_floatundixf.o) has no symbols
/usr/bin/install -c -m 644 libgcov.a ../../.././gcc/ppc64/
chmod 644 ../../.././gcc/ppc64/libgcov.a
ranlib -c ../../.././gcc/ppc64/libgcov.a
parts="crt2.o crt3.o";				\
	for file in $parts; do					\
	  rm -f ../../.././gcc/ppc64/$file;		\
	  /usr/bin/install -c -m 644 $file ../../.././gcc/ppc64/;	\
	done
make[2]: *** [all-stage1-target-libgcc] Error 2
make[1]: *** [stage1-bubble] Error 2
make: *** [bootstrap] Error 2
+ '[' -s .bad_compare ']'
+ exit 1
-------------- next part --------------

-- 
Geoffrey Keating <geoffk@apple.com> 
(via an automated GCC regression-testing script.)


More information about the Gcc-regression mailing list