public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Fariborz Jahanian <fjahanian@apple.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [RFH] - Less than optimal code compiling 252.eon -O2 for x86
Date: Mon, 27 Jun 2005 19:56:00 -0000	[thread overview]
Message-ID: <20050627195619.GA12102@redhat.com> (raw)
In-Reply-To: <6269B965-AF17-4FBD-B3ED-B1BA96936380@apple.com>

On Mon, Jun 27, 2005 at 12:21:01PM -0700, Fariborz Jahanian wrote:
> FYI, the change to rtl  in -O2 vs. -O1 is that -O2 includes -fforce- 
> mem which forces memory operands to registers to make memory  
> references common sub-expressions.

Hmm.  I would suspect this is obsolete now.  We'll have forced
everything into "registers" (or something equivalent that we
can work with) during tree optimization.  Any CSEs that can be
made should have been made.


r~

  reply	other threads:[~2005-06-27 19:56 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 [this message]
2005-06-27 21:52     ` Fariborz Jahanian
2005-06-30 16:04       ` fjahanian
2005-06-30 16:08         ` Andrew Pinski
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=20050627195619.GA12102@redhat.com \
    --to=rth@redhat.com \
    --cc=fjahanian@apple.com \
    --cc=gcc@gcc.gnu.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).