public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/51275] CLOBBERS can be optimized if they are right before the return (or RESX)
Date: Wed, 23 Nov 2011 14:36:00 -0000	[thread overview]
Message-ID: <bug-51275-4-IkRMxeUMlr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51275-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Michael Matz <matz at gcc dot gnu.org> 2011-11-23 14:12:11 UTC ---
Andrew: yes, I considered something similar.  To work really well it requires
some changes to the conflict generation code, though.  Without the clobbers
all objects stay live on the exit-block entry and therefore conflict (and
hence won't be shared).  Conflicts generated only because of the exit block
need to be ignored.

As Jakub says, the implementation should be improved by walking from the exit
block upwards. fab seems like the wrong place to do this.  Something like
DSE feels more natural perhaps.  But it's correct that the removal should
happen after inlining but before eh optimizations.


  parent reply	other threads:[~2011-11-23 14:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23  0:27 [Bug tree-optimization/51275] New: " pinskia at gcc dot gnu.org
2011-11-23  1:18 ` [Bug tree-optimization/51275] " pinskia at gcc dot gnu.org
2011-11-23  2:25 ` pinskia at gcc dot gnu.org
2011-11-23 11:40 ` jakub at gcc dot gnu.org
2011-11-23 14:36 ` matz at gcc dot gnu.org [this message]
2011-11-29 23:05 ` pinskia at gcc dot gnu.org
2011-12-05 15:50 ` rguenth at gcc dot gnu.org
2011-12-05 16:03 ` matz 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-51275-4-IkRMxeUMlr@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).