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/110766] [13 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: in gimple_phi_arg_def_from_edge, at gimple.h:4699
Date: Thu, 27 Jul 2023 10:34:45 +0000 [thread overview]
Message-ID: <bug-110766-4-hqopDCeEVv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110766-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110766
--- Comment #7 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:7004272e9b16e801eb856a991930d81e9c501532
commit r13-7611-g7004272e9b16e801eb856a991930d81e9c501532
Author: Richard Biener <rguenther@suse.de>
Date: Mon Jul 24 08:40:19 2023 +0200
tree-optimization/110766 - missing PHI location check
The following adds a missing PHI location check before querying
the loop latch PHI arg from it.
PR tree-optimization/110766
* tree-scalar-evolution.cc
(analyze_and_compute_bitwise_induction_effect): Check the PHI
is defined in the loop header.
* gcc.dg/torture/pr110766.c: New testcase.
(cherry picked from commit fb132cdfb204bc12851eb1d5852eef6f03c13af3)
next prev parent reply other threads:[~2023-07-27 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 12:27 [Bug tree-optimization/110766] New: " zhendong.su at inf dot ethz.ch
2023-07-21 20:39 ` [Bug tree-optimization/110766] [14 Regression] " pinskia at gcc dot gnu.org
2023-07-21 20:40 ` pinskia at gcc dot gnu.org
2023-07-22 14:20 ` dcb314 at hotmail dot com
2023-07-22 16:36 ` dcb314 at hotmail dot com
2023-07-24 6:31 ` rguenth at gcc dot gnu.org
2023-07-24 7:50 ` cvs-commit at gcc dot gnu.org
2023-07-24 7:51 ` [Bug tree-optimization/110766] [13 " rguenth at gcc dot gnu.org
2023-07-27 10:34 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-27 10:38 ` 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-110766-4-hqopDCeEVv@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).