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 rtl-optimization/52983] [4.8 Regression] internal compiler error: in df_uses_record, at df-scan.c:3243
Date: Mon, 30 Apr 2012 12:11:00 -0000	[thread overview]
Message-ID: <bug-52983-4-a3MGF5tTBY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52983-4@http.gcc.gnu.org/bugzilla/>

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

Alexandre Oliva <aoliva at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2012-04-30
         AssignedTo|unassigned at gcc dot       |aoliva at gcc dot gnu.org
                   |gnu.org                     |
     Ever Confirmed|0                           |1

--- Comment #3 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2012-04-30 12:11:08 UTC ---
Mine.  

1. I have vague recollections of insns that set apparently-dead hw regs
remaining and being relevant for debug stuff, but I no longer remember the
details, and I'm not sure it had to do with the code at hand anyway, or whether
it justifies the current difference.  I'll have to look into that.

2. Yeah, we ought to cleanup_auto_inc_dec the debug expr.  I'll attach the
patch I'm testing momentarily.


  parent reply	other threads:[~2012-04-30 12:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 21:02 [Bug c++/52983] New: " redi at gcc dot gnu.org
2012-04-13 21:02 ` [Bug c++/52983] " redi at gcc dot gnu.org
2012-04-13 21:04 ` [Bug rtl-optimization/52983] [4.8 Regression] " pinskia at gcc dot gnu.org
2012-04-24 13:16 ` jakub at gcc dot gnu.org
2012-04-30 12:11 ` aoliva at gcc dot gnu.org [this message]
2012-04-30 12:16 ` aoliva at gcc dot gnu.org
2012-06-13 20:42 ` aoliva at gcc dot gnu.org
2012-06-28  7:39 ` aoliva at gcc dot gnu.org
2012-07-01  9:22 ` ubizjak at gmail dot com
2012-07-01  9:26 ` ubizjak at gmail dot com
2012-07-02 12:26 ` aoliva at gcc dot gnu.org
2012-07-15 10:58 ` mexas at bristol dot ac.uk
2012-07-30 23:16 ` gary at intrepid dot com
2012-08-02  0:35 ` aoliva at gcc dot gnu.org
2012-08-02  0:36 ` aoliva at gcc dot gnu.org
2012-08-02  0:36 ` aoliva at gcc dot gnu.org
2012-08-02  0:37 ` aoliva at gcc dot gnu.org
2012-08-02  0:37 ` aoliva at gcc dot gnu.org
2012-08-02  2:27 ` aoliva at gcc dot gnu.org
2012-08-04 12:31 ` [Bug debug/52983] " aoliva 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-52983-4-a3MGF5tTBY@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).