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/51879] Missed tail merging with non-const/pure calls
Date: Wed, 18 Jan 2012 10:46:00 -0000	[thread overview]
Message-ID: <bug-51879-4-iBCRQTDw1Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51879-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-01-18 10:36:39 UTC ---
I'm afraid a lot would break.  It really depends on what you use VN for and on
what code.
If you have:
  D.12345_1 = bar (7);
  D.12346_2 = bar (7);
and bar isn't const/pure call, then if VN equivalences D.12345_1 and D.12346_2,
it is wrong.  Of course if you have:
<bb7>:
  D.12345_1 = bar (7);
  goto bb9;
<bb8>:
  D.12346_2 = bar (7);
<bb9>:
  D.12347_3 = PHI <D.12345_1(7), D.12346_2(8)>
(this case), you could VN them the same.


  parent reply	other threads:[~2012-01-18 10:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 11:34 [Bug tree-optimization/51879] New: " jakub at gcc dot gnu.org
2012-01-18  6:14 ` [Bug tree-optimization/51879] " vries at gcc dot gnu.org
2012-01-18 10:46 ` jakub at gcc dot gnu.org [this message]
2012-01-18 10:59 ` rguenth at gcc dot gnu.org
2012-01-18 11:23 ` rguenth at gcc dot gnu.org
2012-01-23 14:51 ` vries at gcc dot gnu.org
2012-01-24 10:21 ` vries at gcc dot gnu.org
2012-01-25 10:10 ` vries at gcc dot gnu.org
2012-02-01 11:20 ` vries at gcc dot gnu.org
2012-04-27  6:13 ` vries at gcc dot gnu.org
2012-04-27  6:29 ` vries at gcc dot gnu.org
2012-04-27  6:36 ` vries at gcc dot gnu.org
2012-07-06 11:22 ` vries at gcc dot gnu.org
2012-07-06 11:22 ` vries at gcc dot gnu.org
2012-07-06 11:22 ` vries at gcc dot gnu.org
2012-07-06 11:31 ` vries 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-51879-4-iBCRQTDw1Q@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).