public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries 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 06:14:00 -0000 [thread overview] Message-ID: <bug-51879-4-PS4v2AJoXt@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 #1 from vries at gcc dot gnu.org 2012-01-18 05:41:34 UTC --- This works for the 3 examples: ... Index: tree-ssa-sccvn.c =================================================================== --- tree-ssa-sccvn.c (revision 182098) +++ tree-ssa-sccvn.c (working copy) @@ -3360,8 +3360,7 @@ visit_use (tree use) /* ??? We should handle stores from calls. */ else if (TREE_CODE (lhs) == SSA_NAME) { - if (!gimple_call_internal_p (stmt) - && gimple_call_flags (stmt) & (ECF_PURE | ECF_CONST)) + if (!gimple_call_internal_p (stmt)) changed = visit_reference_op_call (lhs, stmt); else changed = defs_to_varying (stmt); ... I'll test this to see what breaks.
next prev parent reply other threads:[~2012-01-18 5:41 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 ` vries at gcc dot gnu.org [this message] 2012-01-18 10:46 ` [Bug tree-optimization/51879] " jakub at gcc dot gnu.org 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-PS4v2AJoXt@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: linkBe 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).