public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Macleod <amacleod@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-1135] Propagator should call value_of_stmt. Date: Thu, 16 Jun 2022 18:18:49 +0000 (GMT) [thread overview] Message-ID: <20220616181849.029E13858296@sourceware.org> (raw) https://gcc.gnu.org/g:5b1594dc2d053803ae98ae39f76fbd71f35cb657 commit r13-1135-g5b1594dc2d053803ae98ae39f76fbd71f35cb657 Author: Andrew MacLeod <amacleod@redhat.com> Date: Thu Mar 31 09:36:59 2022 -0400 Propagator should call value_of_stmt. When evaluating the LHS of a stmt, its more efficent/better to call value_of_stmt directly rather than value_of_expr. * tree-ssa-propagate.cc (before_dom_children): Call value_of_stmt. Diff: --- gcc/tree-ssa-propagate.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/tree-ssa-propagate.cc b/gcc/tree-ssa-propagate.cc index c10ffd91766..5983f029364 100644 --- a/gcc/tree-ssa-propagate.cc +++ b/gcc/tree-ssa-propagate.cc @@ -813,7 +813,7 @@ substitute_and_fold_dom_walker::before_dom_children (basic_block bb) tree lhs = gimple_get_lhs (stmt); if (lhs && TREE_CODE (lhs) == SSA_NAME) { - tree sprime = substitute_and_fold_engine->value_of_expr (lhs, stmt); + tree sprime = substitute_and_fold_engine->value_of_stmt (stmt, lhs); if (sprime && sprime != lhs && may_propagate_copy (lhs, sprime)
reply other threads:[~2022-06-16 18:18 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220616181849.029E13858296@sourceware.org \ --to=amacleod@gcc.gnu.org \ --cc=gcc-cvs@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).