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, 20 Nov 2012 08:38:00 -0000	[thread overview]
Message-ID: <bug-55094-4-6eVwKjt8Se@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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-11-20 08:38:22 UTC ---
Author: jakub
Date: Tue Nov 20 08:38:11 2012
New Revision: 193649

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193649
Log:
    PR middle-end/55094
    * builtins.c (expand_builtin_trap): Add REG_ARGS_SIZE note
    on the trap insn for !ACCUMULATE_OUTGOING_ARGS.
    * cfgcleanup.c (outgoing_edges_match): Don't look at debug insns
    on the first old_insns_match_p call.  For !ACCUMULATE_OUTGOING_ARGS
    fail if the last real insn doesn't have REG_ARGS_SIZE note.

    * gcc.dg/pr55094.c: New test.

Added:
    trunk/gcc/testsuite/gcc.dg/pr55094.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/builtins.c
    trunk/gcc/cfgcleanup.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2012-11-20  8:38 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
2012-11-19 17:38 ` jakub at gcc dot gnu.org
2012-11-20  8:38 ` jakub at gcc dot gnu.org [this message]
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-6eVwKjt8Se@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).