public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/52132] [4.7 Regression] ICE in loc_descriptor
Date: Mon, 06 Feb 2012 10:24:00 -0000	[thread overview]
Message-ID: <bug-52132-4-qfSR5fFSfI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52132-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-02-06 10:23:31 UTC ---
Created attachment 26581
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26581
gcc47-pr52132.patch

Untested fix.  What get_true_reg does might be reasonable for code where we
have quite strict requirements on what SUBREG can be applied or not, but it is
definitely wrong for arbitrary SUBREGs in DEBUG_INSNs.  In fact, I don't see
what get_true_reg would buy us, we get at the real REG in for_each_rtx anyway
and can keep the SUBREGs, FLOAT_EXTEND etc. in the DEBUG_INSN.


  parent reply	other threads:[~2012-02-06 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06  8:32 [Bug debug/52132] New: " jakub at gcc dot gnu.org
2012-02-06  8:33 ` [Bug debug/52132] " jakub at gcc dot gnu.org
2012-02-06  8:34 ` jakub at gcc dot gnu.org
2012-02-06 10:24 ` jakub at gcc dot gnu.org [this message]
2012-02-06 23:00 ` p.finizio at gmail dot com
2012-02-06 23:02 ` p.finizio at gmail dot com
2012-02-07 15:49 ` rguenth at gcc dot gnu.org
2012-02-11  8:28 ` jakub at gcc dot gnu.org
2012-02-11  8:32 ` 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-52132-4-qfSR5fFSfI@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).