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/100923] [9/10/11 Regression] wrong code at -O2 and above on x86_64-linux-gnu
Date: Wed, 07 Jul 2021 14:06:52 +0000 [thread overview]
Message-ID: <bug-100923-4-AdqgBoQac5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100923-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100923
--- Comment #8 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:2afae9ff16c45747e8e9c2ad477d28ee159fb1f7
commit r11-8697-g2afae9ff16c45747e8e9c2ad477d28ee159fb1f7
Author: Richard Biener <rguenther@suse.de>
Date: Tue Jun 8 12:52:12 2021 +0200
tree-optimization/100923 - fix alias-ref construction wrt availability
This PR shows that building an ao_ref from value-numbers is prone to
expose bogus contextual alias info to the oracle. The following makes
sure to construct ao_refs from SSA names available at the program point
only.
On the way it modifies the awkward valueize_refs[_1] API.
2021-06-08 Richard Biener <rguenther@suse.de>
PR tree-optimization/100923
* tree-ssa-sccvn.c (valueize_refs_1): Take a pointer to
the operand vector to be valueized.
(valueize_refs): Likewise.
(valueize_shared_reference_ops_from_ref): Adjust.
(valueize_shared_reference_ops_from_call): Likewise.
(vn_reference_lookup_3): Likewise.
(vn_reference_lookup_pieces): Likewise. Re-valueize
with honoring availability when we are about to create
the ao_ref and valueized before.
(vn_reference_lookup): Likewise.
(vn_reference_insert_pieces): Adjust.
* gcc.dg/torture/pr100923.c: New testcase.
(cherry picked from commit 7a56d3d3e99cc77ad8a6a674870c814da6225675)
next prev parent reply other threads:[~2021-07-07 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 10:34 [Bug tree-optimization/100923] New: wrong code at -Os " zhendong.su at inf dot ethz.ch
2021-06-05 11:43 ` [Bug tree-optimization/100923] " zhendong.su at inf dot ethz.ch
2021-06-06 20:57 ` [Bug tree-optimization/100923] wrong code at -O2 " pinskia at gcc dot gnu.org
2021-06-06 20:58 ` [Bug tree-optimization/100923] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2021-06-06 21:02 ` pinskia at gcc dot gnu.org
2021-06-07 9:23 ` rguenth at gcc dot gnu.org
2021-06-07 10:20 ` rguenth at gcc dot gnu.org
2021-06-08 13:09 ` cvs-commit at gcc dot gnu.org
2021-06-08 13:10 ` [Bug tree-optimization/100923] [9/10/11 " rguenth at gcc dot gnu.org
2021-07-07 14:06 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-22 8:02 ` [Bug tree-optimization/100923] [9/10 " rguenth at gcc dot gnu.org
2022-02-17 10:48 ` cvs-commit at gcc dot gnu.org
2022-05-27 9:05 ` [Bug tree-optimization/100923] [9 " rguenth at gcc dot gnu.org
2024-05-06 13:12 ` cvs-commit 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-100923-4-AdqgBoQac5@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).