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 Regression] wrong code at -O2 and above on x86_64-linux-gnu
Date: Mon, 06 May 2024 13:12:43 +0000 [thread overview]
Message-ID: <bug-100923-4-LgMoBtKiPY@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 #11 from GCC 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:7c469a9fc785505dc350aba60311812c2bb0c1b5
commit r15-204-g7c469a9fc785505dc350aba60311812c2bb0c1b5
Author: Richard Biener <rguenther@suse.de>
Date: Wed Feb 28 10:08:31 2024 +0100
tree-optimization/100923 - re-do VN with contextual PTA info fix
The following implements the gist of the PR100923 fix in a leaner
(and more complete) way by realizing that all ao_ref_init_from_vn_reference
uses need to have an SSA name in the base valueized with availability
in mind. Instead of re-valueizing the whole chain of operands we can
simply only and always valueize the SSA name we put in the base.
This handles also two omitted places in vn_reference_lookup_3.
PR tree-optimization/100923
* tree-ssa-sccvn.cc (ao_ref_init_from_vn_reference): Valueize
base SSA_NAME.
(vn_reference_lookup_3): Adjust vn_context_bb around calls
to ao_ref_init_from_vn_reference.
(vn_reference_lookup_pieces): Revert original PR100923 fix.
(vn_reference_lookup): Likewise.
prev parent reply other threads:[~2024-05-06 13:12 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
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 [this message]
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-LgMoBtKiPY@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).