public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rakdver at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/32183] Gcc 4.3 revision 125030 miscompiles 482.sphinx3 in SPEC CPU 2006
Date: Fri, 01 Jun 2007 23:13:00 -0000 [thread overview]
Message-ID: <20070601231320.12902.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32183-682@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from rakdver at gcc dot gnu dot org 2007-06-01 23:13 -------
(In reply to comment #2)
> Is that OK to transform
>
> float sf;
> ...
> sf = 500 * sf;
> for (i = 0; i < ceplen; i++)
> sum[i] *= sf;
>
> to
>
> for (i = 0; i < ceplen; i++)
> sum[i] = (sum[i]* 500)*sf;
>
> You can certainly get the different results when sf is small and sum[i] is
> large.
with -ffast-math, this transformation is ok (although it does not seem to make
sense to do it, it moves a multiplication into a loop).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32183
next prev parent reply other threads:[~2007-06-01 23:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 21:35 [Bug tree-optimization/32183] New: " hjl at lucon dot org
2007-06-01 22:13 ` [Bug tree-optimization/32183] " hjl at lucon dot org
2007-06-01 23:09 ` hjl at lucon dot org
2007-06-01 23:13 ` rakdver at gcc dot gnu dot org [this message]
2007-06-02 0:01 ` [Bug tree-optimization/32183] -fast-math causes a missed optimization to happen pinskia at gcc dot gnu dot org
2007-06-02 0:11 ` hjl at lucon dot org
2007-06-02 0:21 ` [Bug tree-optimization/32183] reassoc can more extra calculations into a loop pinskia at gcc dot gnu dot org
2007-06-02 0:24 ` pinskia at gcc dot gnu dot org
2007-06-02 0:26 ` pinskia at gcc dot gnu dot org
2007-06-02 0:38 ` [Bug tree-optimization/32183] [4.3 Regression] reassoc2 " pinskia at gcc dot gnu dot org
2007-06-02 0:43 ` hjl at lucon dot org
2007-06-02 0:46 ` pinskia at gcc dot gnu dot org
2007-06-02 0:56 ` pinskia at gcc dot gnu dot org
2007-06-02 0:59 ` pinskia at gcc dot gnu dot org
2007-06-02 2:00 ` hjl at lucon dot org
2007-06-02 2:24 ` pinskia at gcc dot gnu dot org
2007-06-02 7:49 ` rakdver at kam dot mff dot cuni dot cz
2007-06-02 14:20 ` hjl at lucon dot org
2007-06-03 22:41 ` hjl at lucon dot org
2007-06-04 21:14 ` hjl at lucon dot org
2007-06-04 21:39 ` hjl at lucon dot org
2007-06-04 22:15 ` rakdver at kam dot mff dot cuni dot cz
2007-06-04 22:19 ` hjl at lucon dot org
2007-06-04 22:39 ` rakdver at kam dot mff dot cuni dot cz
2007-06-04 22:45 ` rakdver at gcc dot gnu dot org
2007-06-04 23:01 ` dberlin at dberlin dot org
2007-06-04 23:23 ` rakdver at kam dot mff dot cuni dot cz
2007-06-04 23:34 ` rakdver at gcc dot gnu dot org
2007-06-04 23:35 ` rakdver at gcc dot gnu dot org
2007-06-05 0:12 ` dberlin at dberlin dot org
2007-06-05 0:15 ` hjl at lucon dot org
2007-06-05 16:45 ` hjl at lucon dot org
2007-06-07 3:16 ` hjl at lucon dot org
2007-06-29 18:38 ` mmitchel at gcc dot gnu dot org
2007-09-08 6:47 ` hjl at gcc dot gnu dot org
2007-10-10 4:08 ` hjl at lucon dot org
2007-10-10 8:58 ` steven at gcc dot gnu dot org
2007-10-10 17:43 ` Daniel Berlin
2007-10-10 17:44 ` dberlin at dberlin dot org
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=20070601231320.12902.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).