public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/47614] cpu2000 benchmark 301.apsi fails with revision 169782
Date: Fri, 04 Feb 2011 22:48:00 -0000 [thread overview]
Message-ID: <bug-47614-4-GXg97Jz0CU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47614-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47614
Pat Haugen <pthaugen at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bergner at gcc dot gnu.org,
| |meissner at gcc dot
| |gnu.org, wschmidt at gcc
| |dot gnu.org
--- Comment #1 from Pat Haugen <pthaugen at gcc dot gnu.org> 2011-02-04 22:47:57 UTC ---
Premature bug creation before...
301.apsi started failing on PowerPC with r169782. Attatched testcase was
compiled with 'gfortran -S -m64 -mcpu=power7 -O3 -funroll-loops -ffast-math'.
Following is good/bad snippet of the assembler.
r169781:
xsmaxdp 0,0,11
ble 7,.L2
mr 10,5
addi 0,7,-2
lfdu 5,8(10)
rlwinm 8,0,0,29,31
li 9,1
xscmpudp 0,0,5
ble 0,.L2
r169782:
xsmaxdp 0,0,11
ble 7,.L2
xscmpudp 0,0,11
addi 0,7,-2
mr 10,5
rlwinm 8,0,0,29,31
li 9,1
ble 0,.L2
Note in the new version that the lfdu instruction is gone. This doesn't affect
the compare since the memory value in f11 is still valid, the problem is that
elminating the lfdu instruction elminates the increment of r10 which causes
problems later on when it is used in subsequent loads (and is pointing at the
wrong location).
next prev parent reply other threads:[~2011-02-04 22:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 22:34 [Bug rtl-optimization/47614] New: " pthaugen at gcc dot gnu.org
2011-02-04 22:48 ` pthaugen at gcc dot gnu.org [this message]
2011-02-07 12:09 ` [Bug rtl-optimization/47614] [4.6 Regression] " rguenth at gcc dot gnu.org
2011-02-07 12:50 ` ebotcazou at gcc dot gnu.org
2011-02-07 12:51 ` rguenth at gcc dot gnu.org
2011-02-07 18:36 ` ebotcazou at gcc dot gnu.org
2011-02-07 19:19 ` jakub at gcc dot gnu.org
2011-02-07 21:22 ` pthaugen at gcc dot gnu.org
2011-02-08 14:54 ` jakub at gcc dot gnu.org
2011-02-08 21:18 ` pthaugen at gcc dot gnu.org
2011-02-09 18:32 ` jakub at gcc dot gnu.org
2011-02-09 18:42 ` jakub at gcc dot gnu.org
2011-02-09 18:48 ` ebotcazou at gcc dot gnu.org
2011-02-09 18:52 ` jakub at gcc dot gnu.org
2011-02-09 21:06 ` pthaugen at gcc dot gnu.org
2011-02-09 21:14 ` jakub at gcc dot gnu.org
2011-02-11 20:55 ` pthaugen at gcc dot gnu.org
2011-02-11 22:33 ` pthaugen at gcc dot gnu.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=bug-47614-4-GXg97Jz0CU@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).