public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "Martin Liška" <mliska@suse.cz>, "GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC] [PATCH] Introduce configure flag --with-stage1-cflags.
Date: Fri, 26 May 2017 11:59:00 -0000	[thread overview]
Message-ID: <CAFiYyc0q8fKcSZ2FwKuXW7V_niNzN4kBUYouwwYUrkWkohx5Qg@mail.gmail.com> (raw)
In-Reply-To: <20170526115155.GL8499@tucnak>

On Fri, May 26, 2017 at 1:51 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Fri, May 26, 2017 at 01:46:47PM +0200, Richard Biener wrote:
>> On Thu, May 25, 2017 at 11:23 AM, Martin Liška <mliska@suse.cz> wrote:
>> > Hello.
>> >
>> > After a discussion with Richi, using adding "-O2" to STAGE1 cflags with a recent
>> > enough compiler can significantly speed up bootstrap. Thus I'm suggesting to
>> > introduce --with-stage1-cflags where one can provide such options.
>>
>> I don't think this is necessary -- you can always override with STAGE1_CFLAGS.
>>
>> > Apart from that, maybe it would be handy to automatically enable "-O2" when
>> > one has a recent compiler? Do we have an example where we detect host compiler
>> > and it's version?
>>
>> Don't know about version but configury already detects that we use GCC, so that
>> knowledge should be readily available.
>
> Well, it certainly shouldn't be -O2 by default for any system GCC, more
> something like if it is major of the configured configure minus 1 or newer
> (or minus 2?), then use -O2, otherwise default to -O0 as before.

I'd still default to -O0 on release branches regardless of version and then
for development we can probably simply use "any GCC" when people have
the chance to override.

At least for me host GCC 4.8 works quite well with -O2.

Richard.

>         Jakub

  reply	other threads:[~2017-05-26 11:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25  9:26 Martin Liška
2017-05-26 11:47 ` Richard Biener
2017-05-26 11:55   ` Jakub Jelinek
2017-05-26 11:59     ` Richard Biener [this message]
2017-05-26 13:02       ` Martin Liška
2017-05-26 13:19         ` Martin Liška
2017-06-19 10:51         ` Martin Liška
2017-06-19 12:30           ` Richard Biener
2017-07-31  7:48             ` Martin Liška
2017-08-25 20:49               ` Jeff Law
2017-08-28 12:55                 ` Richard Biener
2017-08-30 12:19                   ` Martin Liška
2017-05-29 11:35 ` Eric Botcazou
2017-05-30  7:00   ` Richard Biener
2017-05-30 10:30     ` Eric Botcazou
2017-05-30 10:33       ` Martin Liška
2017-05-30 11:12         ` Eric Botcazou

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=CAFiYyc0q8fKcSZ2FwKuXW7V_niNzN4kBUYouwwYUrkWkohx5Qg@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=mliska@suse.cz \
    /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).