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/107447] [13 Regression] ICE: verify_flow_info failed (error: returns_twice call is not first in basic block 2)
Date: Fri, 28 Oct 2022 13:07:26 +0000 [thread overview]
Message-ID: <bug-107447-4-SmZ9fSnJl2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107447-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107447
--- Comment #3 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:1add3635563b39e3c0e9bed4930d11b3f605fdd3
commit r13-3545-g1add3635563b39e3c0e9bed4930d11b3f605fdd3
Author: Richard Biener <rguenther@suse.de>
Date: Fri Oct 28 14:20:36 2022 +0200
tree-optimization/107447 - avoid hoisting returns-twice calls in LIM
The following makes sure to not hoist returns-twice calls in LIM
since we have no way to move the abnormal edge associated with it
and we are prone having stray abnormal edges in the IL which will
then cause IL verification failures even when the actual call
does not return twice.
PR tree-optimization/107447
* tree-ssa-loop-im.cc (determine_max_movement): Do not
hoist returns-twice calls.
* gcc.dg/torture/pr107447.c: New testcase.
next prev parent reply other threads:[~2022-10-28 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 2:59 [Bug tree-optimization/107447] New: " asolokha at gmx dot com
2022-10-28 12:06 ` [Bug tree-optimization/107447] " rguenth at gcc dot gnu.org
2022-10-28 12:20 ` rguenth at gcc dot gnu.org
2022-10-28 13:07 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-28 13:07 ` 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-107447-4-SmZ9fSnJl2@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).