public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55920] [4.8 Regression] ICE in expand_debug_locations, at cfgexpand.c:3753
Date: Tue, 15 Jan 2013 12:19:00 -0000	[thread overview]
Message-ID: <bug-55920-4-wGl0gF9ulc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55920-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #7 from Martin Jambor <jamborm at gcc dot gnu.org> 2013-01-15 12:18:40 UTC ---
(In reply to comment #6)
> Created attachment 29168 [details]
> gcc48-pr55920.patch
> 
> Looking at the #c3 patch, I wonder if this wouldn't be more appropriate
> (untested so far).  It tries to match roughly what the modify_this_stmt
> case does a few lines before.

Yes, that's what I had in mind for 4.9.  I wanted the #c3 patch to be
minimal, given that we are now in stage 4 and we were even considering
reverting patches.  But if it is OK now, I'll be more than happy to
test it and commit it.


  parent reply	other threads:[~2013-01-15 12:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 16:30 [Bug tree-optimization/55920] New: " rmansfield at qnx dot com
2013-01-09 17:47 ` [Bug tree-optimization/55920] " jakub at gcc dot gnu.org
2013-01-09 18:23 ` [Bug tree-optimization/55920] [4.8 Regression] " rguenth at gcc dot gnu.org
2013-01-11 16:53 ` jamborm at gcc dot gnu.org
2013-01-11 16:56 ` jamborm at gcc dot gnu.org
2013-01-11 17:05 ` jakub at gcc dot gnu.org
2013-01-15 12:04 ` jakub at gcc dot gnu.org
2013-01-15 12:19 ` jamborm at gcc dot gnu.org [this message]
2013-01-15 16:34 ` jakub at gcc dot gnu.org
2013-01-15 16:43 ` jamborm at gcc dot gnu.org
2013-01-15 18:37 ` 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-55920-4-wGl0gF9ulc@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).