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 tree-optimization/106249] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 Date: Mon, 11 Jul 2022 07:41:21 +0000 [thread overview] Message-ID: <bug-106249-4-opRhMdBZuV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106249-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106249 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Maybe just make frontend / user inserted __builtin_unreachable ()s trap but not middle-end inserted ones which are generally only to aid DCE? Thus, rewrite them at gimplification time instead of hacking the delcs to be the same?
next prev parent reply other threads:[~2022-07-11 7:41 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-11 5:05 [Bug tree-optimization/106249] New: " asolokha at gmx dot com 2022-07-11 5:32 ` [Bug tree-optimization/106249] [13 Regression] " pinskia at gcc dot gnu.org 2022-07-11 7:38 ` rguenth at gcc dot gnu.org 2022-07-11 7:39 ` rguenth at gcc dot gnu.org 2022-07-11 7:41 ` rguenth at gcc dot gnu.org [this message] 2022-07-12 16:10 ` asolokha at gmx dot com 2022-07-13 7:15 ` [Bug tree-optimization/106249] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 since r13-1450-gd2a898666609452e marxin at gcc dot gnu.org 2022-07-13 7:36 ` cvs-commit at gcc dot gnu.org 2022-07-13 7:36 ` rguenth at gcc dot gnu.org 2022-07-14 17:26 ` pinskia at gcc dot gnu.org 2022-07-26 9:27 ` jakub at gcc dot gnu.org 2022-12-20 14:35 ` rguenth at gcc dot gnu.org 2023-02-08 11:45 ` asolokha at gmx dot com 2023-02-10 10:17 ` 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-106249-4-opRhMdBZuV@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).