public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Eric Botcazou <ebotcazou@adacore.com>,
	Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [RFC] [PATCH] Introduce configure flag --with-stage1-cflags.
Date: Tue, 30 May 2017 10:33:00 -0000	[thread overview]
Message-ID: <501b870c-ab03-319b-e174-47f63813f1f9@suse.cz> (raw)
In-Reply-To: <8222700.x4IQrGbyC3@polaris>

On 05/30/2017 11:43 AM, Eric Botcazou wrote:
>> Are you sure?  In my experience -O2 gets the most test coverage during
>> lifetime of a particular release.
> 
> Yes, some older GCC releases have aliasing issues that are exposed at -O2 only 
> because of -fstrict-aliasing and -fschedule-insns.
> 

That's why we decided to enable -O2 just with GCC 4.8+.

Martin

  reply	other threads:[~2017-05-30 10:30 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
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 [this message]
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=501b870c-ab03-319b-e174-47f63813f1f9@suse.cz \
    --to=mliska@suse.cz \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --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).