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/106781] [13 Regression] ICE: verify_flow_info failed (error: returns_twice call is not first in basic block 2) since r13-1754-g7a158a5776f5ca95
Date: Wed, 19 Oct 2022 08:56:02 +0000 [thread overview]
Message-ID: <bug-106781-4-tqixKEqpqv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106781-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106781
--- Comment #7 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:32ab9238d86dfa6d74d3592bec570f4f257d0413
commit r13-3370-g32ab9238d86dfa6d74d3592bec570f4f257d0413
Author: Richard Biener <rguenther@suse.de>
Date: Wed Oct 19 09:01:56 2022 +0200
tree-optimization/106781 - adjust cgraph lhs removal
The following matches up the cgraph code removing LHS of a noreturn
call with what fixup_noreturn_call does which gets along without
inserting a definition, fixing the ICE resulting from having no
place to actually insert that new def.
PR tree-optimization/106781
* cgraph.cc (cgraph_edge::redirect_call_stmt_to_callee): Copy
LHS removal from fixup_noreturn_call.
* gcc.dg/pr106781.c: New testcase.
next prev parent reply other threads:[~2022-10-19 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 7:11 [Bug tree-optimization/106781] New: [13 Regression] ICE: verify_flow_info failed (error: returns_twice call is not first in basic block 2) asolokha at gmx dot com
2022-08-31 7:48 ` [Bug tree-optimization/106781] " amonakov at gcc dot gnu.org
2022-08-31 8:23 ` [Bug tree-optimization/106781] [13 Regression] ICE: verify_flow_info failed (error: returns_twice call is not first in basic block 2) since r13-1754-g7a158a5776f5ca95 marxin at gcc dot gnu.org
2022-08-31 8:24 ` marxin at gcc dot gnu.org
2022-08-31 8:59 ` amonakov at gcc dot gnu.org
2022-08-31 12:17 ` rguenth at gcc dot gnu.org
2022-08-31 13:37 ` amonakov at gcc dot gnu.org
2022-10-19 7:01 ` rguenth at gcc dot gnu.org
2022-10-19 8:56 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-19 8:56 ` 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-106781-4-tqixKEqpqv@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).