public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63661] [4.9/5 Regression] -O2 miscompiles with -mtune=nehalem or corei7
Date: Mon, 24 Nov 2014 12:22:00 -0000 [thread overview]
Message-ID: <bug-63661-4-zrG5tarBZl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63661-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63661
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |renlin.li at arm dot com
--- Comment #22 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #21)
> It was fixed by r217783 on trunk and the fix also works
> on 4.9 branch. Is is the real fix?
I am not familiar enough with IRA to be really sure but I would say
that yes. This bug really looks as if IRA and LRA chose the same
register (r12) for a different thing, which is described as the
problem in the email accompanying the patch. The weird sequence
clobbering the register certainly goes away with just this patch
applied.
So let's wait for a week or so if any of the RA people confirm this or
have any comments and prepare a backport if they don't.
next prev parent reply other threads:[~2014-11-24 12:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 19:03 [Bug target/63661] New: -O2 miscompiles on OSX 10.10 Yosemite vbraun.name at gmail dot com
2014-10-27 19:05 ` [Bug target/63661] " vbraun.name at gmail dot com
2014-10-27 19:18 ` vbraun.name at gmail dot com
2014-10-28 9:01 ` rguenth at gcc dot gnu.org
2014-10-28 10:46 ` vbraun.name at gmail dot com
2014-10-28 12:08 ` howarth at bromo dot med.uc.edu
2014-10-28 12:12 ` howarth at bromo dot med.uc.edu
2014-10-28 12:13 ` howarth at bromo dot med.uc.edu
2014-10-28 12:14 ` howarth at bromo dot med.uc.edu
2014-10-28 12:24 ` howarth at bromo dot med.uc.edu
2014-10-28 12:27 ` howarth at bromo dot med.uc.edu
2014-10-28 12:44 ` howarth at bromo dot med.uc.edu
2014-10-28 14:36 ` rguenth at gcc dot gnu.org
2014-10-28 14:40 ` [Bug target/63661] [4.9/5 Regression] " rguenth at gcc dot gnu.org
2014-10-29 8:01 ` jakub at gcc dot gnu.org
2014-10-29 8:20 ` jakub at gcc dot gnu.org
2014-10-30 10:37 ` jakub at gcc dot gnu.org
2014-10-30 18:27 ` vbraun.name at gmail dot com
2014-10-31 10:28 ` jamborm at gcc dot gnu.org
2014-11-03 3:02 ` mednafen at gmail dot com
2014-11-21 17:51 ` [Bug target/63661] [4.9/5 Regression] -O2 miscompiles with -mtune=nehalem or corei7 jamborm at gcc dot gnu.org
2014-11-21 21:15 ` hjl.tools at gmail dot com
2014-11-24 12:22 ` jamborm at gcc dot gnu.org [this message]
2014-11-24 13:41 ` rguenth at gcc dot gnu.org
2014-11-26 16:11 ` renlin.li at arm dot com
2014-11-28 11:02 ` renlin at gcc dot gnu.org
2014-11-28 11:19 ` renlin at gcc dot gnu.org
2014-11-28 21:22 ` vbraun.name at gmail dot com
2014-12-01 13:08 ` [Bug target/63661] [4.9 " jakub at gcc dot gnu.org
2014-12-01 18:34 ` jamborm at gcc dot gnu.org
2014-12-03 11:14 ` renlin at gcc dot gnu.org
2014-12-03 16:03 ` renlin.li at arm 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-63661-4-zrG5tarBZl@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).