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/104464] [12 Regression] ICE: in gimple_expand_vec_cond_expr, at gimple-isel.cc:268 with -O -fnon-call-exceptions -fno-tree-dce -fno-tree-forwprop -fsignaling-nans Date: Mon, 17 Apr 2023 10:44:57 +0000 [thread overview] Message-ID: <bug-104464-4-A71U32aNAy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104464-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104464 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:cfd4a86221bc647eaa1c418eb777499250804df6 commit r11-10631-gcfd4a86221bc647eaa1c418eb777499250804df6 Author: Richard Biener <rguenther@suse.de> Date: Wed Feb 9 14:52:24 2022 +0100 middle-end/104464 - ISEL and non-call EH #2 The following adjusts the earlier change to still allow an uncritical replacement. 2022-02-09 Richard Biener <rguenther@suse.de> PR middle-end/104464 * gimple-isel.cc (gimple_expand_vec_cond_expr): Postpone throwing check to after unproblematic replacement. * gcc.dg/pr104464.c: New testcase. (cherry picked from commit 8f8f8c68b434eb32756284dd8e80cfbdff524a20)
prev parent reply other threads:[~2023-04-17 10:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-09 12:38 [Bug tree-optimization/104464] New: " zsojka at seznam dot cz 2022-02-09 13:42 ` [Bug tree-optimization/104464] " rguenth at gcc dot gnu.org 2022-02-09 14:50 ` cvs-commit at gcc dot gnu.org 2022-02-09 14:54 ` rguenth at gcc dot gnu.org 2023-04-17 10:44 ` cvs-commit at gcc dot gnu.org [this message]
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-104464-4-A71U32aNAy@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: linkBe 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).