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/112961] [13 Regression] middle-end Missed vectorization: failed to vectorize simple reduction max since GCC-13
Date: Wed, 08 May 2024 11:50:01 +0000 [thread overview]
Message-ID: <bug-112961-4-knRaxSkjG2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112961-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112961
--- Comment #11 from GCC 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:25add4b65a3bac262685d290a4dc93884a022576
commit r13-8719-g25add4b65a3bac262685d290a4dc93884a022576
Author: Richard Biener <rguenther@suse.de>
Date: Wed Dec 13 08:45:58 2023 +0100
tree-optimization/112991 - re-do PR112961 fix
The following does away with the fake edge adding as in the original
PR112961 fix and instead exposes handling of entry PHIs as additional
parameter of the region VN run.
PR tree-optimization/112991
PR tree-optimization/112961
* tree-ssa-sccvn.h (do_rpo_vn): Add skip_entry_phis argument.
* tree-ssa-sccvn.cc (do_rpo_vn): Likewise.
(do_rpo_vn_1): Likewise, merge with auto-processing.
(run_rpo_vn): Adjust.
(pass_fre::execute): Likewise.
* tree-if-conv.cc (tree_if_conversion): Revert last change.
Value-number latch block but disable value-numbering of
entry PHIs.
* tree-ssa-uninit.cc (execute_early_warn_uninitialized): Adjust.
* gcc.dg/torture/pr112991.c: New testcase.
* g++.dg/vect/pr112961.cc: Likewise.
(cherry picked from commit 93db32a4146afd2a6d90410691351a56768167c9)
next prev parent reply other threads:[~2024-05-08 11:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 14:44 [Bug c/112961] New: " juzhe.zhong at rivai dot ai
2023-12-11 15:33 ` [Bug tree-optimization/112961] " pinskia at gcc dot gnu.org
2023-12-11 15:34 ` [Bug tree-optimization/112961] [13/14 Regression] " pinskia at gcc dot gnu.org
2023-12-11 15:34 ` pinskia at gcc dot gnu.org
2023-12-12 7:21 ` rguenth at gcc dot gnu.org
2023-12-12 12:49 ` rguenth at gcc dot gnu.org
2023-12-12 14:14 ` cvs-commit at gcc dot gnu.org
2023-12-12 14:15 ` [Bug tree-optimization/112961] [13 " rguenth at gcc dot gnu.org
2023-12-12 22:50 ` juzhe.zhong at rivai dot ai
2023-12-13 7:33 ` rguenth at gcc dot gnu.org
2023-12-13 7:35 ` juzhe.zhong at rivai dot ai
2023-12-13 8:44 ` cvs-commit at gcc dot gnu.org
2023-12-13 8:44 ` rguenth at gcc dot gnu.org
2024-05-08 11:50 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-08 11:51 ` 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-112961-4-knRaxSkjG2@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).