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/55094] [4.7/4.8 Regression] ICE in maybe_record_trace_start, at dwarf2cfi.c:2224
Date: Tue, 13 Nov 2012 14:31:00 -0000	[thread overview]
Message-ID: <bug-55094-4-RmGrkgZaRF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55094-4@http.gcc.gnu.org/bugzilla/>


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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-11-13
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |rth at gcc dot gnu.org,
                   |                            |vmakarov at gcc dot gnu.org
     Ever Confirmed|0                           |1

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-11-13 14:31:11 UTC ---
Doesn't ICE on the trunk anymore since LRA merge, apparently because LRA
decides for some reason to use frame pointer anyway, despite
-fomit-frame-pointer -Os.
CCing Vlad to see why.  Apparently it happens in:
665          if (ep->from_rtx == XEXP (x, 0)
666              || (ep->to_rtx == XEXP (x, 0)
667              && ep->to_rtx != hard_frame_pointer_rtx))
668            setup_can_eliminate (ep, false);
where ep->from_rtx is (frame), ep->to_rtx is (sp) and x is (pre_dec:SI
(reg/f:SI 7 sp)).
Is that intentional?

Anyway, testcase that also ICEs on 4.7 branch is e.g.
extern int puts (const char *);
int x;

int
main (int argc, char **argv)
{
  if (argc)
    {
      puts (argv[0]);
      x = 1;
      __builtin_unreachable ();
    }
  x = 1;
  __builtin_unreachable ();
}
with the same options - similar reason, crossjumping during jump2 crossjumps
bbs with different ARGS_SIZE final depth.  For noreturn calls we've handled it
by adding REG_ARGS_SIZE note on the noreturn call I think, for unconditional
TRAP_IF we perhaps could do the same, but not sure what we can do for
__builtin_unreachable which expands to nothing..., with no outgoing edge from
the bb at all.


  parent reply	other threads:[~2012-11-13 14:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-27  2:43 [Bug debug/55094] New: " d.g.gorbachev at gmail dot com
2012-10-29 14:36 ` [Bug debug/55094] " rguenth at gcc dot gnu.org
2012-11-13 14:31 ` jakub at gcc dot gnu.org [this message]
2012-11-19 17:38 ` jakub at gcc dot gnu.org
2012-11-20  8:38 ` jakub at gcc dot gnu.org
2012-11-20  8:43 ` [Bug debug/55094] [4.7 " jakub at gcc dot gnu.org
2012-12-06 16:09 ` rguenth at gcc dot gnu.org
2013-02-01 14:00 ` jakub at gcc dot gnu.org
2013-02-01 14:25 ` 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-55094-4-RmGrkgZaRF@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).