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)
If I opened something new for you and you're interested in the details
I can send here what is needed (then please tell me what exactly is
needed).
P.S. I ask because according to the warning the result should not
change if giving the variable an initial value, but it does.
--
Nothing but perfection
Vladimir A. Pavlov
