This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFH] - Less than optimal code compiling 252.eon -O2 for x86

From: Fariborz Jahanian <fjahanian at apple dot com>
To: Richard Henderson <rth at redhat dot com>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 27 Jun 2005 14:50:21 -0700
Subject: Re: [RFH] - Less than optimal code compiling 252.eon -O2 for x86
References: <B7C12C01-DBA8-4F56-9DF3-4BE0C45D5ADD@apple.com> <6269B965-AF17-4FBD-B3ED-B1BA96936380@apple.com> <20050627195619.GA12102@redhat.com>

On Jun 27, 2005, at 12:56 PM, Richard Henderson wrote:

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.

I will do sanity check followed by SPEC runs (x86 and ppc darwin) and see if behavior changes by obsoleting -fforce-mem in -O2 (or higher).

- Thanks, fariborz

r~

Follow-Ups:
- Re: [RFH] - Less than optimal code compiling 252.eon -O2 for x86
  - From: fjahanian

References:
- [RFH] - Less than optimal code compiling 252.eon -O2 for x86
  - From: Fariborz Jahanian
- Re: [RFH] - Less than optimal code compiling 252.eon -O2 for x86
  - From: Fariborz Jahanian
- Re: [RFH] - Less than optimal code compiling 252.eon -O2 for x86
  - From: Richard Henderson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]