public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: "Martin Liška" <mliska@suse.cz>,
	"Richard Biener" <richard.guenther@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC] [PATCH] Introduce configure flag --with-stage1-cflags.
Date: Fri, 25 Aug 2017 20:49:00 -0000	[thread overview]
Message-ID: <b8c778a1-4eb7-649e-633f-e91296a1d5e1@redhat.com> (raw)
In-Reply-To: <bdf9f849-f903-3a61-b569-b83de94a1204@suse.cz>

On 07/31/2017 01:47 AM, Martin Liška wrote:
> I would like to ping this. Input from other people will be appreciated ;)
I think the thing to keep in mind here is that IIUC this only affects
things when we've configured using the --with-stage1-cflags option.

So questions about is -O1 more stable than -O2, should we restrict -O2
to newer compilers, etc are really more about the defaults we set.

My understanding is the patch is just adding the capability and does not
change the default.  Assuming that's the case, then I'm comfortable
acking the raw infrastructure.

jeff

  reply	other threads:[~2017-08-25 19:51 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
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 [this message]
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=b8c778a1-4eb7-649e-633f-e91296a1d5e1@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=mliska@suse.cz \
    --cc=richard.guenther@gmail.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).