From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2250 invoked by alias); 17 Sep 2008 16:02:11 -0000 Received: (qmail 1602 invoked by uid 48); 17 Sep 2008 16:00:50 -0000 Date: Wed, 17 Sep 2008 16:02:00 -0000 Message-ID: <20080917160050.1600.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug testsuite/37561] [4.4 Regression] Revision 140405 caused g++.old-deja/g++.mike/warn1.C 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: 2008-09/txt/msg02041.txt.bz2 ------- Comment #1 from janis at gcc dot gnu dot org 2008-09-17 16:00 ------- I tested with -m32 on powerpc64-linux, not with both -m32/-m64 which would have caught this; I'll test with both for related patches. The test previously used { dg-warning "" }, which matched any message from that line. The patch, in preparation to using new versions of dg-error and dg-warning that actually check for "warning" and "error", changed that to { dg-error "lvalue" }, which matches the error message for -m32 but not the warning message for -m64. It's a bug in the compiler that the error isn't reported for -m64, and the change to the test merely detected that. This should be a C++ bug, not a testsuite bug. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37561