This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/25241] DejaGNU does not distinguish between errors and warnings
- From: "joseph at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Jan 2007 19:11:20 -0000
- Subject: [Bug testsuite/25241] DejaGNU does not distinguish between errors and warnings
- References: <bug-25241-1000@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #14 from joseph at codesourcery dot com 2007-01-31 19:11 -------
Subject: Re: DejaGNU does not distinguish between errors
and warnings
On Wed, 31 Jan 2007, manu at gcc dot gnu dot org wrote:
> However, I don't see how we can avoid to have our own directives (either
> wrapped dg-* or either custom dg-gcc-*), since the difference between them
> depend on GCC, so it will make dejagnu not useful for other projects. We even
> have differences within GCC: gfortran uses its own style for diagnostics, that
> is why my patch has to restore the original directives for gfortran.exp!
The answer to that is that DejaGnu should provide hooks that testsuites
can use to classify diagnostics. Then GCC would provide such hooks saying
what's a warning or error, gfortran.exp would provide different hooks, and
without hooks from a testsuite DejaGnu could stay compatible with the old
behavior.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25241