From: Fariborz Jahanian <fjahanian@apple.com>
To: law@redhat.com
Cc: Bernd Schmidt <bernds_cb1@t-online.de>,
Steven Bosscher <stevenb@suse.de>,
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 19:06:00 -0000 [thread overview]
Message-ID: <DA02021B-4192-42DB-BB1E-D50FAC3D8386@apple.com> (raw)
In-Reply-To: <1120155806.4621.233.camel@localhost.localdomain>
On Jun 30, 2005, at 11:23 AM, Jeffrey A Law wrote:
> On Thu, 2005-06-30 at 20:12 +0200, Bernd Schmidt wrote:
>
>> Jeffrey A Law wrote:
>>
>>> I'd tend to agree. I'd rather see the option go away than linger on
>>> if the option is no longer useful.
>>>
>>
>> I wouldn't mind that, but I'd also like to point out that there are
>> Makefiles out there which hard-code things like -fforce-mem. Do
>> we want
>> to keep the option as a stub to avoid breaking them?
>>
> Excellent point. I believe in other cases we've kept the option
> around for a release, then killed it.
I would also like to keep this feature around for a while. It is
possible that setting of this option under -O2/-O3 has masked some
optimization bugs. In which case, addition of -fforce-mem would be a
temporary workaround.
- fariborz
>
> jeff
>
>
>
>
next prev parent reply other threads:[~2005-06-30 19:06 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
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 [this message]
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=DA02021B-4192-42DB-BB1E-D50FAC3D8386@apple.com \
--to=fjahanian@apple.com \
--cc=bernds_cb1@t-online.de \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=rth@redhat.com \
--cc=stevenb@suse.de \
/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).