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/53740] New: [4.8 Regression] --enable-checking=yes,rtl bootstrap failure with ada
Date: Thu, 21 Jun 2012 06:54:00 -0000	[thread overview]
Message-ID: <bug-53740-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 53740
           Summary: [4.8 Regression] --enable-checking=yes,rtl bootstrap
                    failure with ada
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Keywords: ice-checking, ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: jakub@gcc.gnu.org
                CC: aoliva@gcc.gnu.org


Last night my x86_64-linux bootstrap failed due to a RTL checking failure.
.../gnat1 -gnatwa -quiet -nostdinc -O2 -g -gnatpg -m32 -mtune=generic
-march=x86-64 -gnatO s-arit64.o s-arit64.adb -o /tmp/s-arit64.s
ICEs, because in dead_debug_insert_temp during DCE
          reg = *DF_REF_REAL_LOC (cur->use);
assigns reg a DEBUG_EXPR rather than REG, so when we later:
          /* Hmm...  Something's fishy, we should be setting REG here.  */
          if (REGNO (dest) != REGNO (reg))
            breg = NULL;
we ICE, because REGNO on DEBUG_EXPR isn't valid.  Alex, could you please look
at it?  Not sure if DEBUG_EXPR there is supposed to be valid and we should just
handle it, or if the problem is that some dead_debug* call wasn't called or
didn't do the right job.  Thanks.


             reply	other threads:[~2012-06-21  6:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21  6:54 jakub at gcc dot gnu.org [this message]
2012-06-21  6:58 ` [Bug debug/53740] " jakub at gcc dot gnu.org
2012-06-21  9:33 ` rguenth at gcc dot gnu.org
2012-06-25  5:26 ` aoliva at gcc dot gnu.org
2012-06-25 13:26 ` rsandifo at gcc dot gnu.org
2012-06-25 14:21 ` rsandifo at gcc dot gnu.org
2012-06-26 20:27 ` aoliva at gcc dot gnu.org
2012-06-27  5:42 ` aoliva at gcc dot gnu.org
2012-06-27  5:58 ` jakub at gcc dot gnu.org
2012-06-28  7:40 ` aoliva at gcc dot gnu.org
2012-06-28  7:46 ` 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-53740-4@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).