From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 574 invoked by alias); 25 May 2011 15:14:02 -0000 Received: (qmail 562 invoked by uid 22791); 25 May 2011 15:14:02 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 25 May 2011 15:13:48 +0000 Received: (qmail 23413 invoked from network); 25 May 2011 15:13:48 -0000 Received: from unknown (HELO ?192.168.1.4?) (janisjo@127.0.0.2) by mail.codesourcery.com with ESMTPA; 25 May 2011 15:13:48 -0000 Message-ID: <4DDD1CFD.1050508@codesourcery.com> Date: Wed, 25 May 2011 16:18:00 -0000 From: Janis Johnson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: gcc-patches@gcc.gnu.org Subject: Re: [testsuite] ignore irrelevant warning in two ARM tests References: <4DDBEE23.60808@codesourcery.com> <4DDC16CB.20209@codesourcery.com> <4DDC3451.1030103@codesourcery.com> <21D392C9-8C20-42D4-A929-DAE7F33A6A1F@comcast.net> In-Reply-To: <21D392C9-8C20-42D4-A929-DAE7F33A6A1F@comcast.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2011-05/txt/msg01880.txt.bz2 On 05/24/2011 05:49 PM, Mike Stump wrote: > On May 24, 2011, at 3:42 PM, Janis Johnson wrote: >>>> Is this one OK for trunk and 4.6? The failure occurs for arm-none-eabi >>>> and for arm-none-linux-gnueabi. >>> >>> You should repeat all the original options from the main dg-options line, >>> with -Wno-abi added, in the ARM EABI dg-options line, since only one >>> dg-options line will be in effect. >> >> Oops, yet again. I'll do that. > > Ok with that change. Also, if there are many of these exceptions, it might be better to add the flags to shut it up to the base set of flags, and then to add it explicitly to any testcase that really does want to test the warning. These are the only tests I've found that get this message. Janis