From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22242 invoked by alias); 31 Jan 2007 19:11:35 -0000 Received: (qmail 22194 invoked by alias); 31 Jan 2007 19:11:20 -0000 Date: Wed, 31 Jan 2007 19:11:00 -0000 Message-ID: <20070131191120.22193.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug testsuite/25241] DejaGNU does not distinguish between errors and warnings In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "joseph at codesourcery dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-01/txt/msg02751.txt.bz2 ------- 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