gcc-4.2-20061212 building error using unsafe *FLAGS

Andrew Haley aph@redhat.com
Tue Feb 13 09:57:00 GMT 2007


Vladimir A. Pavlov writes:
 > On Monday 12 February 2007 01:32, Brian Dessent wrote:
 > > Add --disable-werror to configure.  It's a option because it's common
 > > to run into this.Well,
 > 
 > Thanks for the reply.
 > 
 > But I made another "quick fix" for the code (namely, I initialized 
 > the variable cond with zero value) and got the following result when
 > compiling with _default_ *FLAGS:
 > 
 > 1. The following test failures disappeared:
 > 
 > FAIL: gcc.target/i386/vectorize1.c (internal compiler error)
 > FAIL: gcc.target/i386/vectorize1.c (test for excess errors)
 > 
 > 2. A new one appeared:
 > 
 > FAIL: gcc.dg/noncompile/920923-1.c  -O2  (test for excess errors)
 > 
 > Moreover, there was only one another file with a warning, that file
 > being gcc-4.2-20061212/gcc/sched-rgn.c. Fixing the warning in it in the
 > similar way I got two more errors:
 > 
 > FAIL: gcc.dg/init-bad-1.c near (test for errors, line 44)
 > FAIL: gcc.dg/init-bad-1.c (test for excess errors)

So you're building a broken snapshot.  It would make far more sense to
use a more recent one, or preferably grab the current SVN.

Andrew.



More information about the Gcc-help mailing list