From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28869 invoked by alias); 31 Jan 2007 17:34:41 -0000 Received: (qmail 28799 invoked by uid 48); 31 Jan 2007 17:34:24 -0000 Date: Wed, 31 Jan 2007 17:34:00 -0000 Message-ID: <20070131173424.28798.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: "janis at gcc dot gnu dot org" 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/msg02740.txt.bz2 ------- Comment #11 from janis at gcc dot gnu dot org 2007-01-31 17:34 ------- The other DejaGnu procs that are wrapped in the GCC testsuite, like dg-test, are used within the .exp files, not within tests; that's why dg-error and dg-warning are different. Developers are familiar with test directives but most have probably never looked inside the .exp files. Ben Elliston is also a DejaGnu maintainer, and we've talked about fixing things like this in DejaGnu and moving GCC to a new version. One problem is that it's difficult to move GCC to newer tools; another is that in this case, the behavior isn't compatible if we keep the same names. Perhaps we should back up and design new test directives for diagnostics from scratch, starting by coming up with a list of requirements for them. That might be easier to do on the wiki. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25241