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/110924] [14 Regression] ICE on valid code at -O{s,2,3} on x86_64-linux-gnu: verify_ssa failed
Date: Tue, 08 Aug 2023 12:24:34 +0000 [thread overview]
Message-ID: <bug-110924-4-7KIsdEAK41@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110924-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110924
--- Comment #13 from CVS 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:31ec413098bd334115aff73fc755e49afd3ac371
commit r14-3076-g31ec413098bd334115aff73fc755e49afd3ac371
Author: Richard Biener <rguenther@suse.de>
Date: Tue Aug 8 12:46:42 2023 +0200
tree-optimization/110924 - fix vop liveness for noreturn const CFG parts
The virtual operand live problem used by sinking assumes we have
virtual uses at each end point of the CFG but as shown in the PR
this isn't true for parts for example ending in __builtin_unreachable.
The following removes the optimization made possible by this and
now requires marking backedges.
PR tree-optimization/110924
* tree-ssa-live.h (virtual_operand_live): Update comment.
* tree-ssa-live.cc (virtual_operand_live::get_live_in): Remove
optimization, look at each predecessor.
* tree-ssa-sink.cc (pass_sink_code::execute): Mark backedges.
* gcc.dg/torture/pr110924.c: New testcase.
next prev parent reply other threads:[~2023-08-08 12:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 23:20 [Bug tree-optimization/110924] New: " zhendong.su at inf dot ethz.ch
2023-08-07 0:27 ` [Bug tree-optimization/110924] [14 Regression] " pinskia at gcc dot gnu.org
2023-08-07 0:31 ` pinskia at gcc dot gnu.org
2023-08-07 0:44 ` pinskia at gcc dot gnu.org
2023-08-07 7:07 ` dcb314 at hotmail dot com
2023-08-07 7:15 ` pinskia at gcc dot gnu.org
2023-08-07 7:27 ` pinskia at gcc dot gnu.org
2023-08-07 7:37 ` dcb314 at hotmail dot com
2023-08-08 7:19 ` dcb314 at hotmail dot com
2023-08-08 8:49 ` rguenth at gcc dot gnu.org
2023-08-08 9:36 ` rguenth at gcc dot gnu.org
2023-08-08 9:38 ` rguenth at gcc dot gnu.org
2023-08-08 9:42 ` rguenth at gcc dot gnu.org
2023-08-08 10:26 ` rguenth at gcc dot gnu.org
2023-08-08 12:24 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-08 12:24 ` 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-110924-4-7KIsdEAK41@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).