public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47989] -mrecip causes 482.sphinx3, 464.h264ref and 481.wrf to miscompare
Date: Thu, 10 Mar 2011 13:27:00 -0000 [thread overview]
Message-ID: <bug-47989-4-DfcJ7xxOTc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47989-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47989
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|-mrecip causes 482.sphinx3 |-mrecip causes 482.sphinx3,
|and 464.h264ref to |464.h264ref and 481.wrf to
|miscompare |miscompare
--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-10 13:27:22 UTC ---
Same for 481.wrf, hope for dealing with this with taking into account context
of the division vanishes here. The code is obfuscated with several
levels of array lookup.
In all cases the Intel compiler simply only uses rcp instructions for
vectorized loops.
next prev parent reply other threads:[~2011-03-10 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 14:38 [Bug target/47989] New: -mrecip causes 482.sphinx3 " rguenth at gcc dot gnu.org
2011-03-04 16:06 ` [Bug target/47989] -mrecip causes 482.sphinx3 and 464.h264ref " rguenth at gcc dot gnu.org
2011-03-10 13:27 ` rguenth at gcc dot gnu.org [this message]
2011-03-10 14:01 ` [Bug target/47989] -mrecip causes 482.sphinx3, 464.h264ref and 481.wrf " dominiq at lps dot ens.fr
2011-10-20 15:14 ` uros at gcc dot gnu.org
2011-10-20 15:30 ` ubizjak at gmail dot com
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=bug-47989-4-DfcJ7xxOTc@http.gcc.gnu.org/bugzilla/ \
--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).