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/95171] ICE: verify_flow_info failed (error: wrong outgoing edge flags at end of bb 2)
Date: Mon, 18 May 2020 10:28:13 +0000 [thread overview]
Message-ID: <bug-95171-4-e4WbZncsUP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95171-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95171
--- Comment #4 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:fe168751c5c1c517c7c89c9a1e4e561d66b24663
commit r11-451-gfe168751c5c1c517c7c89c9a1e4e561d66b24663
Author: Richard Biener <rguenther@suse.de>
Date: Mon May 18 08:51:23 2020 +0200
middle-end/95171 - inlining of trapping compare into non-call EH fn
This fixes always-inlining across -fnon-call-exception boundaries
for conditions which we do not allow to throw.
2020-05-18 Richard Biener <rguenther@suse.de>
PR middle-end/95171
* tree-inline.c (remap_gimple_stmt): Split out trapping compares
when inlining into a non-call EH function.
* gcc.dg/pr95171.c: New testcase.
next prev parent reply other threads:[~2020-05-18 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 4:55 [Bug tree-optimization/95171] New: " asolokha at gmx dot com
2020-05-18 5:52 ` [Bug tree-optimization/95171] " marxin at gcc dot gnu.org
2020-05-18 6:04 ` rguenth at gcc dot gnu.org
2020-05-18 6:26 ` rguenth at gcc dot gnu.org
2020-05-18 10:28 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-18 10:28 ` rguenth at gcc dot gnu.org
2020-05-20 11:28 ` rguenth at gcc dot gnu.org
2020-12-01 15:44 ` cvs-commit at gcc dot gnu.org
2021-09-16 1:36 ` pinskia 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-95171-4-e4WbZncsUP@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).