From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 71856 invoked by alias); 16 Dec 2015 22:59:15 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 71845 invoked by uid 89); 16 Dec 2015 22:59:14 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 16 Dec 2015 22:59:13 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id 8FFD932D3BB; Wed, 16 Dec 2015 22:59:12 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tBGMxAYx029122; Wed, 16 Dec 2015 17:59:11 -0500 Message-ID: <5671ECBE.5070305@redhat.com> Date: Wed, 16 Dec 2015 22:59:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Simon Marchi CC: "Jose E. Marchesi" , Yao Qi , "gdb@sourceware.org" Subject: Re: C++ conversion status update References: <565460FB.6070103@redhat.com> <86zixdnlfg.fsf@gmail.com> <566F13D4.9000900@redhat.com> <877fkglytf.fsf@oracle.com> <5671C65E.3070503@redhat.com> <5671E16C.1080907@redhat.com> In-Reply-To: <5671E16C.1080907@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-12/txt/msg00025.txt.bz2 On 12/16/2015 10:10 PM, Pedro Alves wrote: > "When an unrecognized warning option is requested (e.g., -Wunknown-warning), GCC emits a > diagnostic stating that the option is not recognized. However, if the -Wno- form is used, the > behavior is slightly different: no diagnostic is produced for -Wno-unknown-warning unless other > diagnostics are being produced. This allows the use of new -Wno- options with old > compilers, but if something goes wrong, the compiler warns that an unrecognized > option is present." > > I think we can handle this by making that warning-support test code > check whether -Wfoo works when we actually want -Wno-foo. Proposed fix posted at: https://sourceware.org/ml/gdb-patches/2015-12/msg00312.html Thanks, Pedro Alves