public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103168] Value numbering for PRE of pure functions can be improved
Date: Wed, 24 Nov 2021 11:40:50 +0000 [thread overview]
Message-ID: <bug-103168-4-UtAXuLXURD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103168-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103168
--- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:6180f5c8d6d1dc7b6634c41a46f0f8f5ca2e5b9d
commit r12-5499-g6180f5c8d6d1dc7b6634c41a46f0f8f5ca2e5b9d
Author: Richard Biener <rguenther@suse.de>
Date: Wed Nov 24 09:08:44 2021 +0100
tree-optimization/103168 - Improve VN of pure function calls
This improves value-numbering of calls that read memory, calls
to const functions with aggregate arguments and calls to
pure functions where the latter include const functions we
demoted to pure for the fear of interposing with a less
optimized version. Note that for pure functions we do not
handle functions that access global memory.
2021-11-24 Richard Biener <rguenther@suse.de>
Jan Hubicka <jh@suse.cz>
PR tree-optimization/103168
* ipa-modref.h (struct modref_summary): Add load_accesses.
* ipa-modref.c (modref_summary::finalize): Initialize
load_accesses.
* tree-ssa-sccvn.c (visit_reference_op_call): Use modref
info to walk the virtual use->def chain to CSE const/pure
function calls possibly reading from memory.
* g++.dg/tree-ssa/pr103168.C: New testcase.
next prev parent reply other threads:[~2021-11-24 11:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 11:15 [Bug tree-optimization/103168] New: Value numbering " hubicka at gcc dot gnu.org
2021-11-10 11:16 ` [Bug tree-optimization/103168] " hubicka at gcc dot gnu.org
2021-11-11 9:12 ` [Bug tree-optimization/103168] Value numbering for PRE " rguenth at gcc dot gnu.org
2021-11-17 20:28 ` hubicka at gcc dot gnu.org
2021-11-18 9:13 ` rguenth at gcc dot gnu.org
2021-11-18 9:39 ` hubicka at kam dot mff.cuni.cz
2021-11-18 9:40 ` hubicka at kam dot mff.cuni.cz
2021-11-19 14:21 ` [Bug tree-optimization/103168] [9/10/11/12 Regression] " hubicka at gcc dot gnu.org
2021-11-22 12:54 ` [Bug tree-optimization/103168] " rguenth at gcc dot gnu.org
2021-11-22 13:07 ` hubicka at kam dot mff.cuni.cz
2021-11-22 14:19 ` rguenth at gcc dot gnu.org
2021-11-22 14:24 ` rguenth at gcc dot gnu.org
2021-11-22 15:14 ` hubicka at kam dot mff.cuni.cz
2021-11-22 23:07 ` hubicka at gcc dot gnu.org
2021-11-23 0:26 ` Jan Hubicka
2021-11-23 7:26 ` Jan Hubicka
2021-11-23 0:26 ` hubicka at kam dot mff.cuni.cz
2021-11-23 7:26 ` hubicka at kam dot mff.cuni.cz
2021-11-23 7:43 ` rguenth at gcc dot gnu.org
2021-11-23 7:49 ` hubicka at gcc dot gnu.org
2021-11-24 11:40 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-24 12:06 ` 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-103168-4-UtAXuLXURD@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).