From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-208340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 30391 invoked by alias); 27 Jan 2007 16:56:48 -0000
Received: (qmail 30369 invoked by uid 48); 27 Jan 2007 16:56:38 -0000
Date: Sat, 27 Jan 2007 16:56:00 -0000
Subject: [Bug testsuite/30612]  New: Testsuite cannot detect duplicated error/warning messages
X-Bugzilla-Reason: CC
Message-ID: <bug-30612-13511@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2007-01/txt/msg02360.txt.bz2

We have seen several regressions and PRs with respect to this. It is possible
to workaround this by using:

/* { dg-bogus "message.*message" } */
/* { dg-warning "message" "" { target *-*-* } 1 } */

However, the test must be alone in one file. Otherwise, strange things may
happen.

This is obviously very cumbersome and not practical in the long run.


-- 
           Summary: Testsuite cannot detect duplicated error/warning
                    messages
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: manu at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30612