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/107107] [10/11 Regression] Wrong codegen from TBAA when stores to distinct same-mode types are collapsed?
Date: Mon, 12 Dec 2022 16:33:31 +0000 [thread overview]
Message-ID: <bug-107107-4-qbgBTh5Svs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107107-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107107
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:fa11fc62ddee81a8bc3e69d5e3180695a6dbb666
commit r11-10417-gfa11fc62ddee81a8bc3e69d5e3180695a6dbb666
Author: Richard Biener <rguenther@suse.de>
Date: Thu Oct 6 11:20:16 2022 +0200
tree-optimization/107107 - tail-merging VN wrong-code
The following fixes an unintended(?) side-effect of the special
MODIFY_EXPR expression entries we add for tail-merging during VN.
We shouldn't value-number the virtual operand differently here.
PR tree-optimization/107107
* tree-ssa-sccvn.c (visit_reference_op_store): Do not
affect value-numbering when doing the tail merging
MODIFY_EXPR lookup.
* gcc.dg/pr107107.c: New testcase.
(cherry picked from commit 85333b9265720fc4e49397301cb16324d2b89aa7)
next prev parent reply other threads:[~2022-12-12 16:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 21:34 [Bug middle-end/107107] New: " bugdal at aerifal dot cx
2022-10-01 2:25 ` [Bug middle-end/107107] " bugdal at aerifal dot cx
2022-10-01 2:59 ` pinskia at gcc dot gnu.org
2022-10-01 3:02 ` pinskia at gcc dot gnu.org
2022-10-01 3:05 ` [Bug tree-optimization/107107] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-10-01 3:05 ` pinskia at gcc dot gnu.org
2022-10-01 17:08 ` amonakov at gcc dot gnu.org
2022-10-01 20:01 ` bugdal at aerifal dot cx
2022-10-06 9:02 ` rguenth at gcc dot gnu.org
2022-10-06 9:22 ` rguenth at gcc dot gnu.org
2022-10-06 10:07 ` cvs-commit at gcc dot gnu.org
2022-10-06 10:08 ` [Bug tree-optimization/107107] [10/11/12 " rguenth at gcc dot gnu.org
2022-10-17 13:10 ` cvs-commit at gcc dot gnu.org
2022-12-12 16:33 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-26 13:05 ` [Bug tree-optimization/107107] [10 " cvs-commit at gcc dot gnu.org
2023-01-26 13: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-107107-4-qbgBTh5Svs@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).