From: Marek Polacek <polacek@redhat.com>
To: Steve Ellcey <sellcey@cavium.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Wabi warnings during GCC build
Date: Wed, 27 Jun 2018 16:28:00 -0000 [thread overview]
Message-ID: <20180627160942.GB4896@redhat.com> (raw)
In-Reply-To: <201806271553.w5RFrmvF006768@sellcey-dt.caveonetworks.com>
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.
libstdc++/acinclude.m4 needs to be adjusted:
WARN_FLAGS='-Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi'
I guess to -Wabi=11?
Marek
next prev parent reply other threads:[~2018-06-27 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 16:09 Steve Ellcey
2018-06-27 16:28 ` Marek Polacek [this message]
2018-06-27 17:30 ` Eric Gallager
2018-06-27 20:06 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180627160942.GB4896@redhat.com \
--to=polacek@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=sellcey@cavium.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).