From: Gerald Pfeifer <gerald@pfeifer.com>
To: FX <fxcoudert@gmail.com>
Cc: gcc@gcc.gnu.org, Iain Sandoe <iain@sandoe.co.uk>,
Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: C++11 code in the gcc 10 branch
Date: Thu, 31 Dec 2020 17:52:13 +0100 (CET) [thread overview]
Message-ID: <63a1a158-222e-83b3-e71c-e9955ed23baa@pfeifer.com> (raw)
In-Reply-To: <B9A871FA-94CB-46BF-886A-7EFAC11F32EC@gmail.com>
On Mon, 21 Dec 2020, FX via Gcc wrote:
> I’m trying to bootstrap a GCC 10 compiler on macOS with clang, and I am
> getting errors in stage 1, because there is C++11 code that is rejected
> by clang (because the bootstrap involves compiling stage 1 with
> -std=gnu++98, online on master (see top-level configure.ac).
I got reports from users, too (for FreeBSD with clang as system
compiler), and have them test this patch which looks fine so far.
> These errors are not seen, I believe, when GCC is the bootstrap
> compiler, because GCC will issue a warning instead of an error (as
> clang does).
>
> One place with such issue is in aarch64-builtins.c, which contains a
> C++11 constructor. I can fix it with this:
When are you going to apply your fix that Richard S. approved on the
21st?
Gerald
next prev parent reply other threads:[~2020-12-31 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 14:34 FX
2020-12-21 14:39 ` Iain Sandoe
2020-12-21 14:49 ` Richard Sandiford
2020-12-31 16:52 ` Gerald Pfeifer [this message]
2020-12-31 17:47 ` FX
2020-12-31 17:54 ` Iain Sandoe
2020-12-31 18:45 ` FX
2021-01-01 10:21 ` Iain Sandoe
2020-12-31 17:55 ` Richard Sandiford
2021-01-01 10:28 ` Andreas Schwab
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=63a1a158-222e-83b3-e71c-e9955ed23baa@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=fxcoudert@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=richard.sandiford@arm.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).