public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/105231] [12 Regression] ICE: in rtl_verify_bb_insns, at cfgrtl.cc:2797 (flow control insn inside a basic block) with custom flags since r12-4767-g81342e95827f77c0
Date: Tue, 12 Apr 2022 08:47:55 +0000 [thread overview]
Message-ID: <bug-105231-4-FhdBA4yCSQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105231-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105231
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
may_trap_p triggers on the (float_extend:XF ...) because
/* Any floating arithmetic may trap. */
if (FLOAT_MODE_P (GET_MODE (x)) && flag_trapping_math)
return 1;
with all that I think the proposed change is reasonable.
next prev parent reply other threads:[~2022-04-12 8:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 19:20 [Bug rtl-optimization/105231] New: [12 Regression] ICE: in rtl_verify_bb_insns, at cfgrtl.cc:2797 (flow control insn inside a basic block) with custom flags zsojka at seznam dot cz
2022-04-11 19:25 ` [Bug target/105231] " pinskia at gcc dot gnu.org
2022-04-12 7:46 ` [Bug rtl-optimization/105231] " rguenth at gcc dot gnu.org
2022-04-12 7:49 ` [Bug rtl-optimization/105231] [12 Regression] ICE: in rtl_verify_bb_insns, at cfgrtl.cc:2797 (flow control insn inside a basic block) with custom flags since r12-4767-g81342e95827f77c0 marxin at gcc dot gnu.org
2022-04-12 8:25 ` rguenth at gcc dot gnu.org
2022-04-12 8:42 ` rguenth at gcc dot gnu.org
2022-04-12 8:47 ` rguenth at gcc dot gnu.org [this message]
2022-04-12 9:01 ` ebotcazou at gcc dot gnu.org
2022-04-12 9:15 ` rguenther at suse dot de
2022-04-12 9:29 ` ebotcazou at gcc dot gnu.org
2022-04-12 9:34 ` rguenth at gcc dot gnu.org
2022-04-12 9:36 ` rguenth at gcc dot gnu.org
2022-04-12 9:44 ` rguenth at gcc dot gnu.org
2022-04-12 9:47 ` rguenth at gcc dot gnu.org
2022-04-12 9:57 ` ebotcazou at gcc dot gnu.org
2022-04-12 10:12 ` rguenther at suse dot de
2022-04-12 11:15 ` rguenth at gcc dot gnu.org
2022-04-12 11:23 ` jakub at gcc dot gnu.org
2022-04-12 11:27 ` jakub at gcc dot gnu.org
2022-04-12 11:37 ` rguenther at suse dot de
2022-04-12 11:39 ` jakub at gcc dot gnu.org
2022-04-12 11:47 ` rguenther at suse dot de
2022-04-13 7:37 ` ebotcazou at gcc dot gnu.org
2022-04-13 7:42 ` rguenther at suse dot de
2022-04-13 12:38 ` segher at gcc dot gnu.org
2022-04-13 12:58 ` segher at gcc dot gnu.org
2022-04-14 8:22 ` rguenth at gcc dot gnu.org
2022-04-14 10:43 ` segher at gcc dot gnu.org
2022-04-14 10:55 ` rguenther at suse dot de
2022-04-14 12:16 ` rguenth at gcc dot gnu.org
2022-04-19 15:31 ` rguenth at gcc dot gnu.org
2022-04-25 7:26 ` cvs-commit at gcc dot gnu.org
2022-04-25 7:27 ` rguenth at gcc dot gnu.org
2022-06-29 12:00 ` 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-105231-4-FhdBA4yCSQ@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).