From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 35128 invoked by alias); 2 May 2018 10:13:30 -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 34828 invoked by uid 89); 2 May 2018 10:13:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx3-rdu2.redhat.com (HELO mx1.redhat.com) (66.187.233.73) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 02 May 2018 10:13:26 +0000 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id EAFA476FBA; Wed, 2 May 2018 10:13:24 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id 527B0215CDA7; Wed, 2 May 2018 10:13:24 +0000 (UTC) Subject: Re: GDB 8.1 build error To: Simon Marchi References: <214C80CC-1173-41F6-AAA1-39C9D39E28B2@comcast.net> <454707570722fc0220074c0eca015a8f@polymtl.ca> <6171a043-e486-85ec-bdbb-2077a2b5ebd0@redhat.com> <9ed9617b-987e-3225-8518-a43eda0b5548@redhat.com> <13bcba4a8a70bcd977a7e644dd59e4bf@polymtl.ca> Cc: Paul Koning , gdb@sourceware.org From: Pedro Alves Message-ID: <927fb991-56bd-368c-6056-fc4c06002db4@redhat.com> Date: Wed, 02 May 2018 10:13:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2018-05/txt/msg00003.txt.bz2 On 05/02/2018 10:41 AM, Pedro Alves wrote: > So seems like we could handle this my making --disable-build-warnings > use "-Wno-error -w" instead of just "-w". But I'd suggest checking with > clang and/or gcc folks to confirm the difference is intentional too. A gcc maintainer told me that gcc has behaved like this since forever. So it could be that the difference in clang may be unintentional. Thanks, Pedro Alves