From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2747 invoked by alias); 27 Jun 2018 16:28:40 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 2730 invoked by uid 89); 27 Jun 2018 16:28:40 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mail-ot0-f169.google.com Received: from mail-ot0-f169.google.com (HELO mail-ot0-f169.google.com) (74.125.82.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 27 Jun 2018 16:28:38 +0000 Received: by mail-ot0-f169.google.com with SMTP id h6-v6so2870958otj.0 for ; Wed, 27 Jun 2018 09:28:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gwmail-gwu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TLBkwr8tWk6gTiYLZfSPHVdWfj7R8dkkd5S9DuergG8=; b=EFF/hhZHqkk3ypgmHqtswtG+7tBaOxqZPbXcLs0+92NNPr5Lk8V+RYJL4aI58mWc8k w3qb1RVC1kIWQc7rsdtrkmNBdlG4ktlIbzGXSz/O7SKFwZ6lNwIt7T8Dks7Hy6cESOsn sCKxCCtjCHppJVAaPsxUUnCii0qobmVOCp4EBH9wLyr0IGmWFInY3jwTWIX7/VDsSv5O mKi6ekg/E/ccrlkb6dmuonKGGpkjmOu055LfGeXxEeidHkioervbA0SWfHk/9lUtHvFI nvp6FSv3dQqbjcm+CHp2mlNCyhbZh8+EKsLizR6nEgVuC5xze4KiC3wKxbByEKzEIYbp wtYg== MIME-Version: 1.0 Received: by 2002:a9d:2cb8:0:0:0:0:0 with HTTP; Wed, 27 Jun 2018 09:28:36 -0700 (PDT) In-Reply-To: <20180627160942.GB4896@redhat.com> References: <201806271553.w5RFrmvF006768@sellcey-dt.caveonetworks.com> <20180627160942.GB4896@redhat.com> From: Eric Gallager Date: Wed, 27 Jun 2018 17:30:00 -0000 Message-ID: Subject: Re: Wabi warnings during GCC build To: Marek Polacek Cc: Steve Ellcey , gcc@gcc.gnu.org Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-06/txt/msg00278.txt.bz2 On 6/27/18, Marek Polacek wrote: > On Wed, Jun 27, 2018 at 08:53:48AM -0700, Steve Ellcey wrote: >> Are other people building GCC seeing these messages during the build: >> >> cc1plus: warning: -Wabi won't warn about anything [-Wabi] >> cc1plus: note: -Wabi warns about differences from the most up-to-date ABI, >> which is also used by default >> cc1plus: note: use e.g. -Wabi=11 to warn about changes from GCC 7 >> >> It doesn't seem to be causing any problems in the build (even bootstrap) >> but I am wondering why it is there. It seems to be happening when >> using the latest (just built) g++ to build libstdc++ so it shouldn't >> be related to the system GCC that I am using to build with. >> >> I didn't find any mention of it in the gcc or libstdc++ mailing lists >> when I looked or find any bugzilla report. > > I see it too, started with r261571. Yeah I also see it. > libstdc++/acinclude.m4 needs to be adjusted: > WARN_FLAGS='-Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi' > I guess to -Wabi=11? > > Marek > At first I was going to wonder if it wasn't necessary to remain compatible with old versions of GCC that don't support -Wabi=11, but then I reread the part about this happening with the just-built GCC, so if that warning is only ever used with the just-built GCC, then yeah, I'd guess it'd probably be okay.