This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: test for excess errors

On 23 August 2006 13:58, Jack Howarth wrote:

>    Is it the expected behavior for dejagnu to always report warnings
> as errors in the "test for excess errors" check?

  To be precise, what it checks for is excess messages output to stderr.  It
doesn't discriminate whether they are errors, warnings, or a debugging printf
that you accidentally left in when you compiled!

> Is this a design
> decision or just how dejagnu currently works? 

  I can't say.

> I ask because the
> current output of "test for excess errors" when a FAIL occurs can
> be inaccurate. With -m64 on Darwin we currently get a significant number
> of false positives in the fortran testsuite due to linker warnings being
> mistaken for errors. 

  Hmmm, that's a problem.  We don't really want to be testing the assembler's
or linker's output.  Don't immediately know how you'd get round that without
reworking the testsuite to run the various substages of the compilation
one-at-a-time, or just adding horrible hard-coded filtering to the captured
stderr output...

  Actually, I wonder if "-Wl,2> -Wl,/dev/null" would work!?  (modulo suitable

Can't think of a witty .sigline today....

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]