public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/47614] [4.6 Regression] cpu2000 benchmark 301.apsi fails with revision 169782
Date: Mon, 07 Feb 2011 18:36:00 -0000 [thread overview]
Message-ID: <bug-47614-4-yz4goMEW8V@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
--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-02-07 18:21:23 UTC ---
> A brief look suggests the patch may only change var-tracking behavior, but
> it seems that is not the case.
Quite very brief then. :-) PR 43494 was a wrong code regression and
Alexandre's patch fixed it, that's why I looked at it in the first place after
seeing the double ping.
next prev parent reply other threads:[~2011-02-07 18:22 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 ` [Bug rtl-optimization/47614] " pthaugen at gcc dot gnu.org
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 [this message]
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-yz4goMEW8V@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).