public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "David O'Brien" <obrien@freebsd.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/10189: pentium4 breaks suns libm code for __ieee754_pow(double x, double y)
Date: Sat, 29 Mar 2003 04:06:00 -0000 [thread overview]
Message-ID: <20030329035601.24052.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/10189; it has been noted by GNATS.
From: "David O'Brien" <obrien@freebsd.org>
To: Alexander Leidinger <Alexander@Leidinger.net>
Cc: gcc-gnats@gcc.gnu.org, freebsd-current@freebsd.org, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, ljrittle@gcc.gnu.org
Subject: Re: optimization/10189: pentium4 breaks suns libm code for __ieee754_pow(double x, double y)
Date: Fri, 28 Mar 2003 19:46:27 -0800
On Wed, Mar 26, 2003 at 10:09:34PM +0100, Alexander Leidinger wrote:
> And trust me, as long as gcc ships with a description of other
> optimizations beneath "-O" there will be (clueless or smart... does it
> really matter here?) people which will try those optimizations on
> everything
Not to mention bullshit ones like "-O9". I see that all the time. What
do these poeple think they are buying with that?????
GCC should stop accepting -O values higher than what does anything.
next reply other threads:[~2003-03-29 3:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 4:06 David O'Brien [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 14:32 bangerth
2003-03-26 21:27 Alexander Leidinger
2003-03-26 18:06 David O'Brien
2003-03-26 14:02 ljrittle
2003-03-22 12:46 till
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=20030329035601.24052.qmail@sources.redhat.com \
--to=obrien@freebsd.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).