From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Gabriel Dos Reis <gdr@microsoft.com>,
Andrew Dean <Andrew.Dean@microsoft.com>,
David Malcolm <dmalcolm@redhat.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"ro@CeBiTec.Uni-Bielefeld.DE" <ro@CeBiTec.Uni-Bielefeld.DE>,
"mikestump@comcast.net" <mikestump@comcast.net>,
"jason@redhat.com" <jason@redhat.com>,
Jonathan Wakely <cxx@kayari.org>
Subject: Re: GCC selftest improvements
Date: Mon, 28 Oct 2019 21:41:00 -0000 [thread overview]
Message-ID: <00dcb1c4-793c-c44f-da1b-eabe067c7e1e@redhat.com> (raw)
In-Reply-To: <20191028202713.GF28442@gate.crashing.org>
On 10/28/19 2:27 PM, Segher Boessenkool wrote:
> On Mon, Oct 28, 2019 at 01:40:03PM -0600, Jeff Law wrote:
>> On 10/25/19 6:01 PM, Gabriel Dos Reis wrote:
>>> Jason, Jonathan - is the situation on the terrain really that dire that C++11 (or C++14) isn't at all available for platforms that GCC is bootstrapped from?
>> The argument that I'd make is that's relatively uncommon (I know, I know
>> AIX) that bootstrapping in those environments may well require first
>> building something like gcc-9.
>>
>> I'd really like to see us move to C++11 or beyond. Sadly, I don't think
>> we have any good mechanism for making this kind of technical decision
>> when there isn't consensus.
>
> Which GCC version will be required to work as bootstrap compiler? Will
> 4.8.5 be enough?
I'd say gcc-9. What would we gain by making it 4.8 or anything else
that old?
jeff
next prev parent reply other threads:[~2019-10-28 21:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 20:50 Andrew Dean via gcc
2019-10-24 21:09 ` Jonathan Wakely
2019-10-25 6:17 ` David Malcolm
2019-10-25 22:38 ` Andrew Dean via gcc
2019-10-26 0:01 ` Gabriel Dos Reis via gcc
2019-10-26 22:46 ` Eric Gallager
2019-10-31 15:56 ` Pedro Alves
2019-12-02 2:50 ` Eric Gallager
2020-02-13 0:49 ` [EXTERNAL] " Modi Mo via gcc
2020-02-13 1:53 ` David Malcolm
2020-02-13 2:28 ` Nicholas Krause
2020-02-13 22:18 ` Modi Mo via gcc
2020-02-14 14:55 ` C++11 bootstrap (was: GCC selftest improvements) Jason Merrill
2020-02-14 23:10 ` [EXTERNAL] Re: GCC selftest improvements Segher Boessenkool
2020-02-15 16:14 ` Jeff Law
2020-02-25 19:58 ` Modi Mo via gcc
2020-02-25 22:11 ` David Malcolm
2020-02-25 22:13 ` Gabriel Dos Reis via gcc
2020-03-02 22:19 ` Modi Mo via gcc
2019-10-28 19:40 ` Jeff Law
2019-10-28 19:42 ` Richard Biener
2019-10-28 19:44 ` Jeff Law
2019-10-28 19:46 ` Gabriel Dos Reis via gcc
2019-10-28 20:27 ` Segher Boessenkool
2019-10-28 21:41 ` Jeff Law [this message]
2019-10-28 21:47 ` Jakub Jelinek
2019-10-28 21:52 ` Andrew Pinski
2019-10-28 22:02 ` Jeff Law
2019-10-28 22:03 ` Gabriel Dos Reis via gcc
2019-10-29 8:41 ` Richard Biener
2019-10-31 16:09 ` Pedro Alves
2019-10-28 21:50 ` Iain Sandoe
2019-10-28 22:12 ` Segher Boessenkool
2019-10-29 8:45 ` Richard Biener
2019-11-22 21:02 ` Andrew Dean via gcc
2019-11-22 22:02 ` Segher Boessenkool
2019-11-22 22:36 ` Jakub Jelinek
2019-11-22 23:41 ` Segher Boessenkool
2019-11-23 16:33 ` Jeff Law
2019-11-23 23:03 ` Nicholas Krause
2020-02-14 20:50 ` Mike Stump
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=00dcb1c4-793c-c44f-da1b-eabe067c7e1e@redhat.com \
--to=law@redhat.com \
--cc=Andrew.Dean@microsoft.com \
--cc=cxx@kayari.org \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@microsoft.com \
--cc=jason@redhat.com \
--cc=mikestump@comcast.net \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=segher@kernel.crashing.org \
/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).