From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25072 invoked by alias); 31 Jan 2007 21:15:28 -0000 Received: (qmail 24876 invoked by alias); 31 Jan 2007 21:15:08 -0000 Date: Wed, 31 Jan 2007 21:15:00 -0000 Message-ID: <20070131211508.24875.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: "gdr at cs dot tamu dot edu" 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/msg02757.txt.bz2 ------- Comment #15 from gdr at cs dot tamu dot edu 2007-01-31 21:15 ------- Subject: Re: DejaGNU does not distinguish between errors and warnings "manu at gcc dot gnu dot org" writes: | (In reply to comment #11) | > 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. | | I don't think that they need to, except for the people responsible for | maintaining the testsuite. GCC maintainers are /supposed/ to be familiar with the testsuite framework, fix the testsuite and add more. Well, that is the theory :-) We should fix the broken testcases. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25241