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 target/107209] [13 Regression] ICE: verify_gimple failed (error: statement marked for throw, but doesn't) Date: Fri, 13 Jan 2023 10:01:46 +0000 [thread overview] Message-ID: <bug-107209-4-hP8CSmDUGT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107209-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107209 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>: https://gcc.gnu.org/g:3893c9c0a16832f55d8d0827f50c48a56c52f6e7 commit r13-5137-g3893c9c0a16832f55d8d0827f50c48a56c52f6e7 Author: Richard Biener <rguenther@suse.de> Date: Fri Jan 13 10:01:32 2023 +0000 aarch64: Don't update EH info when folding [PR107209] The AArch64 folders tried to update EH info on the fly, bypassing the folder's attempts to remove dead EH edges later. This triggered an ICE when folding a potentially-trapping call to a constant. gcc/ PR target/107209 * config/aarch64/aarch64.cc (aarch64_gimple_fold_builtin): Don't update EH info on the fly. gcc/testsuite/ * gcc.target/aarch64/pr107209.c: New test. Co-Authored-By: Richard Biener <rguenther@suse.de>
next prev parent reply other threads:[~2023-01-13 10:01 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-11 4:29 [Bug tree-optimization/107209] New: " asolokha at gmx dot com 2022-10-11 7:27 ` [Bug tree-optimization/107209] " rguenth at gcc dot gnu.org 2022-10-11 15:57 ` pinskia at gcc dot gnu.org 2022-10-18 8:08 ` rguenth at gcc dot gnu.org 2022-10-18 8:29 ` [Bug target/107209] " rguenth at gcc dot gnu.org 2022-11-30 17:26 ` jakub at gcc dot gnu.org 2022-12-20 9:22 ` ktkachov at gcc dot gnu.org 2022-12-20 9:29 ` jakub at gcc dot gnu.org 2023-01-13 10:01 ` cvs-commit at gcc dot gnu.org [this message] 2023-01-13 10:09 ` rsandifo 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-107209-4-hP8CSmDUGT@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).