------- Comment #10 from gdr at cs dot tamu dot edu 2007-01-31 06:43 ------- Subject: Re: DejaGNU does not distinguish between errors and warnings
"manu at gcc dot gnu dot org" <[EMAIL PROTECTED]> writes: | (In reply to comment #8) | > This is nice, Manuel, I hadn't considered changing the expressions as they are | > added to the messages list. | | We already wrap dg-test (see the end of lib/gcc-dg.exp). So why not wrapping | dg-warning and dg-error? Unfortunately my approach is quite brute, it would be | better to call the original dg-warning/dg-error, catch its output and adjust it | (or replace it). This way we shouldn't need to copy the whole function. | Something similar is done for dg-test. I don't know how to do this because I | have no idea of Tcl programming. It would be nice, once this is working in GCC, to contribute this back to upstream DejaGnu; I'm sure Rob would be delighted to have them. [...] | Also, we will need a new way to handle the output of inform and | other messages that gcc produces, such as "cc1: warnings being | treated as errors". (I think | that particular message is inconsistent with the rest of our diagnostics, but | that is another issue). inform() from GCC should always prefix with "note: ". If that is not the case, then we have a bug (in the diagnostic machinery). Also. dg-warning, dg-error, should probably augmented with dg-note -- as notes are sometimes emitted as part of diagnostics. We should probably have a "generic" way of adding custom dg-xxx thingy. Last time I fiddled with DejaGnu and GCC testsuite framework was more five years ago... -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25241
