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/105484] [11/12/13 Regression] ICE: verify_flow_info failed: BB 2 cannot throw but has an EH edge with -Os -march=cannonlake -fnon-call-exceptions -fno-tree-dce -fno-tree-forwprop since r11-5074-g287cc750b0887e86 Date: Thu, 05 May 2022 08:37:04 +0000 [thread overview] Message-ID: <bug-105484-4-wUCBTLl8H7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105484-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105484 --- Comment #6 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:e1a41143a2e24c65d94364fd82b165ff71a759d8 commit r13-129-ge1a41143a2e24c65d94364fd82b165ff71a759d8 Author: Richard Biener <rguenther@suse.de> Date: Thu May 5 09:34:59 2022 +0200 tree-optimization/105484 - VEC_SET and EH When the IL representation of VEC_SET is marked as throwing (unnecessarily), we need to clean that when replacing it with the .VEC_SET internal function call which cannot throw. 2022-05-05 Richard Biener <rguenther@suse.de> PR tree-optimization/105484 * gimple-isel.cc (gimple_expand_vec_set_expr): Clean EH, return whether the CFG changed. (gimple_expand_vec_exprs): When the CFG changed, clean it up. * gcc.dg/torture/pr105484.c: New testcase.
next prev parent reply other threads:[~2022-05-05 8:37 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-04 18:37 [Bug tree-optimization/105484] New: [12/13 Regression] ICE: verify_flow_info failed: BB 2 cannot throw but has an EH edge with -Os -march=cannonlake -fnon-call-exceptions -fno-tree-dce -fno-tree-forwprop zsojka at seznam dot cz 2022-05-04 19:22 ` [Bug tree-optimization/105484] [11/12/13 Regression] ICE: verify_flow_info failed: BB 2 cannot throw but has an EH edge with -Os -march=cannonlake -fnon-call-exceptions -fno-tree-dce -fno-tree-forwprop since r11-5074-g287cc750b0887e86 marxin at gcc dot gnu.org 2022-05-05 5:19 ` [Bug target/105484] " crazylht at gmail dot com 2022-05-05 7:18 ` crazylht at gmail dot com 2022-05-05 7:26 ` rguenth at gcc dot gnu.org 2022-05-05 7:37 ` rguenth at gcc dot gnu.org 2022-05-05 8:37 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-05 8:37 ` [Bug target/105484] [11/12 " rguenth at gcc dot gnu.org 2022-05-06 9:28 ` cvs-commit at gcc dot gnu.org 2023-04-17 10:45 ` [Bug target/105484] [11 " cvs-commit at gcc dot gnu.org 2023-04-17 10:45 ` 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-105484-4-wUCBTLl8H7@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).