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 tree-optimization/51117] [4.7 regression] rev.181172 causes glibc build failure
Date: Fri, 09 Dec 2011 16:18:00 -0000	[thread overview]
Message-ID: <bug-51117-4-iZihKyTVit@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51117-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-12-09 16:09:48 UTC ---
Created attachment 26034
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26034
gcc47-pr51117-sink.patch

So far untested attempt to sink clobbers if a BB with all EH pred edges and a
single EH succ edge, ending with internal throwing RESX contains other than
that just CLOBBER stmts (and optionally debug stmts).
Such BBs force us to immediately rethrow with no actual code in between, when
the clobber stmts are sunk into the successor, we can actually ehcleanup those.
Had to tweak a little bit the conflict detection in the expander for that
though, without that it would think the vars still conflict on the incoming
edge (even when no actual insns that might touch memory appear before the
clobber).


  parent reply	other threads:[~2011-12-09 16:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-13 12:42 [Bug tree-optimization/51117] New: " markus at trippelsdorf dot de
2011-11-15 10:50 ` [Bug tree-optimization/51117] " izamyatin at gmail dot com
2011-11-15 16:27 ` matz at gcc dot gnu.org
2011-11-29 19:03 ` rth at gcc dot gnu.org
2011-12-05 14:11 ` rguenth at gcc dot gnu.org
2011-12-05 14:57 ` jakub at gcc dot gnu.org
2011-12-06  1:06 ` jsm28 at gcc dot gnu.org
2011-12-08 17:40 ` jakub at gcc dot gnu.org
2011-12-09 11:54 ` jakub at gcc dot gnu.org
2011-12-09 16:18 ` jakub at gcc dot gnu.org [this message]
2011-12-09 20:52 ` jakub at gcc dot gnu.org
2011-12-13 14:01 ` matz at gcc dot gnu.org
2011-12-13 14:08 ` jakub at gcc dot gnu.org
2011-12-15 17:31 ` 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-51117-4-iZihKyTVit@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).