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/106909] [13 Regression] error: control flow in the middle of basic block since r13-2541-g78ef801b7263606d
Date: Tue, 13 Sep 2022 08:52:44 +0000 [thread overview]
Message-ID: <bug-106909-4-CO4DWVqXNs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106909-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106909
--- Comment #6 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:2c867232df70d3de304714906b4198ecb262eb32
commit r13-2640-g2c867232df70d3de304714906b4198ecb262eb32
Author: Richard Biener <rguenther@suse.de>
Date: Tue Sep 13 08:59:41 2022 +0200
middle-end/106909 - CTRL altering flag after folding
The following makes sure to clear the CTRL altering flag when
folding emits a __builitin_unreachable in place of a virtual call
which now might become a trap.
PR middle-end/106909
* gimple-fold.cc (gimple_fold_call): Clear the ctrl-altering
flag of a unreachable call.
next prev parent reply other threads:[~2022-09-13 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 15:30 [Bug c++/106909] New: error: control flow in the middle of basic block dcb314 at hotmail dot com
2022-09-12 15:43 ` [Bug tree-optimization/106909] " dcb314 at hotmail dot com
2022-09-12 15:46 ` [Bug tree-optimization/106909] [13 Regression] " pinskia at gcc dot gnu.org
2022-09-12 18:48 ` dcb314 at hotmail dot com
2022-09-12 19:49 ` [Bug tree-optimization/106909] [13 Regression] error: control flow in the middle of basic block since r13-2541-g78ef801b7263606d marxin at gcc dot gnu.org
2022-09-13 5:45 ` marxin at gcc dot gnu.org
2022-09-13 6:59 ` rguenth at gcc dot gnu.org
2022-09-13 8:52 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-13 8:53 ` 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-106909-4-CO4DWVqXNs@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).