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/111715] Missed optimization in FRE because of weak TBAA
Date: Mon, 09 Oct 2023 13:20:04 +0000 [thread overview]
Message-ID: <bug-111715-4-es07VXePAs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111715-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111715
--- Comment #4 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:11b8cf1685bb40af5b86653e492e350983025957
commit r14-4510-g11b8cf1685bb40af5b86653e492e350983025957
Author: Richard Biener <rguenther@suse.de>
Date: Mon Oct 9 13:05:10 2023 +0200
tree-optimization/111715 - improve TBAA for access paths with pun
The following improves basic TBAA for access paths formed by
C++ abstraction where we are able to combine a path from an
address-taking operation with a path based on that access using
a pun to avoid memory access semantics on the address-taking part.
The trick is to identify the point the semantic memory access path
starts which allows us to use the alias set of the outermost access
instead of only that of the base of this path.
PR tree-optimization/111715
* alias.cc (reference_alias_ptr_type_1): When we have
a type-punning ref at the base search for the access
path part that's still semantically valid.
* gcc.dg/tree-ssa/ssa-fre-102.c: New testcase.
next prev parent reply other threads:[~2023-10-09 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 15:06 [Bug tree-optimization/111715] New: " rguenth at gcc dot gnu.org
2023-10-06 15:07 ` [Bug tree-optimization/111715] " rguenth at gcc dot gnu.org
2023-10-06 15:09 ` rguenth at gcc dot gnu.org
2023-10-09 11:12 ` rguenth at gcc dot gnu.org
2023-10-09 13:20 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-09 13:20 ` rguenth at gcc dot gnu.org
2023-10-09 21:34 ` sjames at gcc dot gnu.org
2023-10-10 6:46 ` rguenth at gcc dot gnu.org
2023-10-10 6:58 ` sjames 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-111715-4-es07VXePAs@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).