From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 70794 invoked by alias); 27 Jun 2018 15:53:53 -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 70779 invoked by uid 89); 27 Jun 2018 15:53:53 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:729 X-HELO: camailhost.cavium.com Received: from camailhost.cavium.com (HELO camailhost.cavium.com) (12.108.191.230) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 27 Jun 2018 15:53:52 +0000 Received: from sellcey-dt.caveonetworks.com ([10.18.104.136]) by camailhost.cavium.com (8.14.7/8.14.7) with ESMTP id w5RFrmej032016 for ; Wed, 27 Jun 2018 08:53:49 -0700 Received: from sellcey-dt.caveonetworks.com (localhost [127.0.0.1]) by sellcey-dt.caveonetworks.com (8.15.2/8.15.2/Debian-3) with ESMTP id w5RFrmIE006769 for ; Wed, 27 Jun 2018 08:53:48 -0700 Received: (from sellcey@localhost) by sellcey-dt.caveonetworks.com (8.15.2/8.15.2/Submit) id w5RFrmvF006768; Wed, 27 Jun 2018 08:53:48 -0700 Date: Wed, 27 Jun 2018 16:09:00 -0000 From: Steve Ellcey Message-Id: <201806271553.w5RFrmvF006768@sellcey-dt.caveonetworks.com> To: gcc@gcc.gnu.org Subject: Wabi warnings during GCC build Reply-To: sellcey@cavium.com X-SW-Source: 2018-06/txt/msg00276.txt.bz2 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. Steve Ellcey