public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/46931] [4.6 Regression] Subversion id 167184 breaks building perlbench on power7 with debug
Date: Fri, 17 Dec 2010 06:23:00 -0000	[thread overview]
Message-ID: <bug-46931-4-OaLODX7jTR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46931-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46931

--- Comment #6 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2010-12-17 06:23:19 UTC ---
Created attachment 22793
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22793
Patch I'm testing that fixes the bug

Instead of just dropping the debug info on the floor, I figured we could
preserve the RHS of the removed DEF, if unchanging, in the debug stmts
themselves, if this wouldn't create invalid RHS for the debug bind, or in debug
temps bound just before the using debug stmts otherwise.


  parent reply	other threads:[~2010-12-17  6:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 22:54 [Bug regression/46931] New: " meissner at gcc dot gnu.org
2010-12-14  6:00 ` [Bug regression/46931] " hjl.tools at gmail dot com
2010-12-14  8:05 ` jakub at gcc dot gnu.org
2010-12-16 14:15 ` [Bug regression/46931] [4.6 Regression] " rguenth at gcc dot gnu.org
2010-12-16 17:21 ` aoliva at gcc dot gnu.org
2010-12-17  6:15 ` aoliva at gcc dot gnu.org
2010-12-17  6:23 ` aoliva at gcc dot gnu.org [this message]
2010-12-28 20:21 ` [Bug debug/46931] " aoliva at gcc dot gnu.org
2010-12-28 21:01 ` jakub 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-46931-4-OaLODX7jTR@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).