public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/52548] missed PRE optimization when function call follows to-be hoisted variable
Date: Mon, 12 Mar 2012 14:03:00 -0000 [thread overview]
Message-ID: <bug-52548-4-DpCypqZ7hS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52548-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52548
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org
|gnu.org |
--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-12 14:02:59 UTC ---
As discussed, EXP_GEN can be cleaned from invalid mems at generation time,
mem-cleaning should happen separately from clean (), and applied to ANTIC_OUT
instead.
Mine for now, but don't hold your breath.
next prev parent reply other threads:[~2012-03-12 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 21:09 [Bug middle-end/52548] New: " aldyh at gcc dot gnu.org
2012-03-10 0:15 ` [Bug middle-end/52548] " steven at gcc dot gnu.org
2012-03-12 9:50 ` [Bug tree-optimization/52548] " rguenth at gcc dot gnu.org
2012-03-12 14:03 ` rguenth at gcc dot gnu.org [this message]
2012-03-21 11:41 ` rguenth at gcc dot gnu.org
2012-03-21 11:51 ` rguenth at gcc dot gnu.org
2012-03-22 13:17 ` rguenth at gcc dot gnu.org
2012-03-22 13:17 ` rguenth 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-52548-4-DpCypqZ7hS@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).