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 c++/111019] [12/13 Regression] Optimizer incorrectly assumes variable is not changed while change happens through another pointer
Date: Thu, 24 Aug 2023 10:56:10 +0000 [thread overview]
Message-ID: <bug-111019-4-H8C7r4TAIj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111019-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111019
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:c1b5514124ab7a8aceec1ae4a82d2149fc687ecf
commit r13-7753-gc1b5514124ab7a8aceec1ae4a82d2149fc687ecf
Author: Richard Biener <rguenther@suse.de>
Date: Thu Aug 17 15:21:33 2023 +0200
tree-optimization/111019 - invariant motion and aliasing
The following fixes a bad choice in representing things to the alias
oracle by LIM which while correct in pieces is inconsistent with itself.
When canonicalizing a ref to a bare deref instead of leaving the base
object and the extracted offset the same and just substituting an
alternate ref the following replaces the base and the offset as well,
avoiding the confusion that otherwise will arise in
aliasing_matching_component_refs_p.
PR tree-optimization/111019
* tree-ssa-loop-im.cc (gather_mem_refs_stmt): When canonicalizing
also scrap base and offset in case the ref is indirect.
* g++.dg/torture/pr111019.C: New testcase.
(cherry picked from commit 745ec2135aabfbe2c0fb7780309837d17e8986d4)
next prev parent reply other threads:[~2023-08-24 10:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 22:00 [Bug c++/111019] New: " boskidialer at gmail dot com
2023-08-15 8:55 ` [Bug c++/111019] [12/13/14 Regression] " rguenth at gcc dot gnu.org
2023-08-15 12:59 ` ppalka at gcc dot gnu.org
2023-08-15 13:39 ` rguenther at suse dot de
2023-08-15 16:15 ` boskidialer at gmail dot com
2023-08-17 6:49 ` rguenth at gcc dot gnu.org
2023-08-17 12:08 ` rguenth at gcc dot gnu.org
2023-08-17 12:53 ` rguenth at gcc dot gnu.org
2023-08-17 13:00 ` rguenth at gcc dot gnu.org
2023-08-17 13:24 ` rguenth at gcc dot gnu.org
2023-08-18 13:05 ` cvs-commit at gcc dot gnu.org
2023-08-18 13:11 ` [Bug c++/111019] [12/13 " rguenth at gcc dot gnu.org
2023-08-21 11:27 ` boskidialer at gmail dot com
2023-08-24 10:56 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-27 11:35 ` [Bug tree-optimization/111019] [12 " cvs-commit at gcc dot gnu.org
2023-11-27 11:37 ` 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-111019-4-H8C7r4TAIj@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).