public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: fjahanian <fjahanian@apple.com>
Cc: gcc@gcc.gnu.org, Richard Henderson <rth@redhat.com>
Subject: Re: [RFH] - Less than optimal code compiling 252.eon -O2 for x86
Date: Thu, 30 Jun 2005 16:08:00 -0000	[thread overview]
Message-ID: <e7b85ec89a92b2c1861f3383637467e9@physics.uc.edu> (raw)
In-Reply-To: <27918F7A-CBBC-4657-AB29-3242BE6DF53D@apple.com>


On Jun 30, 2005, at 12:05 PM, fjahanian wrote:
> Bootstrapped and dejagnu tested on apple-x86-darwin and 
> apple-ppc-darwin.
>
> We also observed that on ppc, SPEC did not show any performance change 
> either way. On apple-x86-darwin 252.eon improved by 7% as expected, 
> with no noticeable change in other benchmarks. One caveat to all these 
> is that this may expose optimization bugs which were previously hidden 
> by inclusion of -fforce-mem.
>
> OK for check-in?
>
> - fariborz
>
> ChangeLog:
>
> 2005-06-30  Fariborz Jahanian <fjahanian@apple.com>
>
>       * opts.c (decode_options): Don't set -fforce-mem with -O2 and 
> more.

Please also update the docs in invoke.texi.

Thanks,
Andrew Pinski

  reply	other threads:[~2005-06-30 16:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 22:06 Fariborz Jahanian
2005-06-24 22:17 ` Andrew Pinski
2005-06-24 23:46   ` fjahanian
2005-06-25  0:06     ` Steven Bosscher
2005-06-30 14:42       ` fjahanian
2005-06-30 15:03         ` fjahanian
2005-06-27 19:20 ` Fariborz Jahanian
2005-06-27 19:56   ` Richard Henderson
2005-06-27 21:52     ` Fariborz Jahanian
2005-06-30 16:04       ` fjahanian
2005-06-30 16:08         ` Andrew Pinski [this message]
2005-06-30 16:55         ` Steven Bosscher
2005-06-30 17:48           ` Jeffrey A Law
2005-06-30 18:12             ` Bernd Schmidt
2005-06-30 18:19               ` Joe Buck
2005-06-30 18:25                 ` Giovanni Bajo
2005-06-30 18:23               ` Jeffrey A Law
2005-06-30 19:06                 ` Fariborz Jahanian
2005-06-30 19:47                   ` Steven Bosscher
2005-06-30 21:30                     ` Fariborz Jahanian

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=e7b85ec89a92b2c1861f3383637467e9@physics.uc.edu \
    --to=pinskia@physics.uc.edu \
    --cc=fjahanian@apple.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@redhat.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).