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 tree-optimization/54200] copyrename generates wrong debuginfo
Date: Wed, 08 Aug 2012 12:16:00 -0000	[thread overview]
Message-ID: <bug-54200-4-q4g8kg3u0Z@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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
         AssignedTo|unassigned at gcc dot       |rguenth at gcc dot gnu.org
                   |gnu.org                     |

--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-08-08 12:16:06 UTC ---
Created attachment 27962
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27962
patch

Patch which breaks gcc.target/i386/pad-10.c for real (and other testcases
due to dump differences).  We now get the correct

  <bb 4>:
  D.1759_7 = x_3(D) + z_6(D);

  <bb 5>:
  # D.1759_1 = PHI <z_6(D)(3), D.1759_7(4)>
  return D.1759_1;


  parent reply	other threads:[~2012-08-08 12:16 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 [this message]
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
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-q4g8kg3u0Z@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).