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 middle-end/107485] [10 Regression] gcc-10 ICE with -fnon-call-exception Date: Mon, 14 Nov 2022 18:08:53 +0000 [thread overview] Message-ID: <bug-107485-4-A6chOUtIN6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107485-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107485 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:c17873d83aaeed037fb5d039df2e6303d4b6a553 commit r10-11083-gc17873d83aaeed037fb5d039df2e6303d4b6a553 Author: Richard Biener <rguenther@suse.de> Date: Mon Nov 14 17:19:20 2022 +0100 tree-optimization/107485 - fix non-call exception ICE with inlining Inlining performs a wrong non-call exception fixup for VEC_COND_EXPRs which on the branch fail to properly have the condition split out in the first place. PR tree-optimization/107485 * tree-inline.c (remap_gimple_stmt): Use correct type for split out condition of [VEC_]COND_EXPRs.
next prev parent reply other threads:[~2022-11-14 18:08 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-01 3:23 [Bug middle-end/107485] New: " spop at gcc dot gnu.org 2022-11-01 3:40 ` [Bug middle-end/107485] " pinskia at gcc dot gnu.org 2022-11-01 3:41 ` [Bug middle-end/107485] [10 Regression] " pinskia at gcc dot gnu.org 2022-11-01 3:51 ` pinskia at gcc dot gnu.org 2022-11-01 3:56 ` pinskia at gcc dot gnu.org 2022-11-01 3:58 ` pinskia at gcc dot gnu.org 2022-11-05 10:35 ` rguenth at gcc dot gnu.org 2022-11-14 16:18 ` rguenth at gcc dot gnu.org 2022-11-14 18:08 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-14 18:15 ` rguenth at gcc dot gnu.org 2022-11-14 19:19 ` spop 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-107485-4-A6chOUtIN6@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).