public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54200] copyrename generates wrong debuginfo
Date: Thu, 09 Aug 2012 08:06:00 -0000 [thread overview]
Message-ID: <bug-54200-4-9VXPuaQls0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54200-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54200
--- Comment #5 from rguenther at suse dot de <rguenther at suse dot de> 2012-08-09 08:05:51 UTC ---
On Wed, 8 Aug 2012, pinskia at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54200
>
> --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-08-08 15:31:09 UTC ---
> The other thing which copyrename helps is register allocation as it allows out
> of ssa to coalesce some ssa names which could not do before.
Yes, though that's a matter of adjusting what coalescing can
coalesce (which is only limited to the sets it computes conflicts for)
next prev parent reply other threads:[~2012-08-09 8:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 11:14 [Bug tree-optimization/54200] New: " rguenth at gcc dot gnu.org
2012-08-08 11:37 ` [Bug tree-optimization/54200] " rguenth at gcc dot gnu.org
2012-08-08 12:16 ` rguenth at gcc dot gnu.org
2012-08-08 12:22 ` rguenth at gcc dot gnu.org
2012-08-08 15:31 ` pinskia at gcc dot gnu.org
2012-08-09 8:06 ` rguenther at suse dot de [this message]
2012-08-10 14:19 ` rguenth at gcc dot gnu.org
2012-08-13 9:29 ` rguenth at gcc dot gnu.org
2012-08-13 11:55 ` rguenth at gcc dot gnu.org
2012-08-13 12:14 ` izamyatin at gmail dot com
2012-08-13 12:35 ` rguenth at gcc dot gnu.org
2012-08-13 12:47 ` izamyatin at gmail dot com
2013-03-29 15:36 ` jakub at gcc dot gnu.org
2013-04-02 7:56 ` rguenther at suse dot de
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-54200-4-9VXPuaQls0@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).