From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 103244 invoked by alias); 27 Apr 2018 20:16:47 -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 103229 invoked by uid 89); 27 Apr 2018 20:16:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=HContent-Transfer-Encoding:8bit X-HELO: smtp.polymtl.ca Received: from smtp.polymtl.ca (HELO smtp.polymtl.ca) (132.207.4.11) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 27 Apr 2018 20:16:43 +0000 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id w3RKGbUl018307 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 27 Apr 2018 16:16:41 -0400 Received: by simark.ca (Postfix, from userid 112) id 01A211EF60; Fri, 27 Apr 2018 16:16:37 -0400 (EDT) Received: from simark.ca (localhost [127.0.0.1]) by simark.ca (Postfix) with ESMTP id C53251E073; Fri, 27 Apr 2018 16:16:35 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 27 Apr 2018 20:24:00 -0000 From: Simon Marchi To: Pedro Alves Cc: Paul Koning , gdb@sourceware.org Subject: Re: GDB 8.1 build error In-Reply-To: <6171a043-e486-85ec-bdbb-2077a2b5ebd0@redhat.com> References: <214C80CC-1173-41F6-AAA1-39C9D39E28B2@comcast.net> <454707570722fc0220074c0eca015a8f@polymtl.ca> <6171a043-e486-85ec-bdbb-2077a2b5ebd0@redhat.com> Message-ID: X-Sender: simon.marchi@polymtl.ca User-Agent: Roundcube Webmail/1.3.4 X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Fri, 27 Apr 2018 20:16:37 +0000 X-IsSubscribed: yes X-SW-Source: 2018-04/txt/msg00035.txt.bz2 On 2018-04-27 16:00, Pedro Alves wrote: > On 04/27/2018 08:18 PM, Simon Marchi wrote: >> On 2018-04-27 15:08, Pedro Alves wrote: >>> Oh, wait....  Your build line has no "-W" at all, it has "-w" >>> instead?? >>> How did that happen? >> >> When --disable-build-warnings is used, we don't put any -W/-Wno- >> flags: >> >> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gdb/warning.m4;h=f176a3291aa68acf0122609531abb4652425525b;hb=HEAD#l62 > > But then, we add "-w", and I'm surprised that "-w" did not disable > all warnings, including "-Wc++11-narrowing". "-w" is supposed to mean > disable all warnings. At least, that's how GCC behaves. > Could that be a clang bug? On clang at least, -Wnarrowing seems to generate an error by default, so -w doesn't affect it. You get: no flag: error -Wno-error=narrowing: warning -Wno-error=narrowing -w: silent So in this case, we would still need either -Wno-error=narrowing or -Wno-narrowing. We can test if gcc behaves the same, we just need something that is an error by default but we can downgrade to a warning. Do you have an idea of such diagnostic? Simon