public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/114687] [13/14 Regression] ICE: in edge_before_returns_twice_call, at gimple-iterator.cc:981 Date: Thu, 11 Apr 2024 05:59:47 +0000 [thread overview] Message-ID: <bug-114687-4-j0okHIjerH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114687-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114687 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Target Milestone|--- |13.3 Last reconfirmed| |2024-04-11 Known to fail| |14.0 Summary|ICE: in |[13/14 Regression] ICE: in |edge_before_returns_twice_c |edge_before_returns_twice_c |all, at |all, at |gimple-iterator.cc:981 |gimple-iterator.cc:981 Status|UNCONFIRMED |NEW Known to work| |13.2.0 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. I suspect the patches which fixed PR 112709 caused this one which so this is also a regression on the GCC 13 branch too.
next prev parent reply other threads:[~2024-04-11 5:59 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-11 3:47 [Bug sanitizer/114687] New: " iamanonymous.cs at gmail dot com 2024-04-11 5:59 ` pinskia at gcc dot gnu.org [this message] 2024-04-11 6:50 ` [Bug sanitizer/114687] [13/14 Regression] " rguenth at gcc dot gnu.org 2024-04-11 12:47 ` jakub at gcc dot gnu.org 2024-04-11 15:13 ` jakub at gcc dot gnu.org 2024-04-12 9:00 ` cvs-commit at gcc dot gnu.org 2024-04-12 9:01 ` [Bug sanitizer/114687] [13 " jakub at gcc dot gnu.org 2024-04-21 4:09 ` cvs-commit at gcc dot gnu.org 2024-04-23 6:44 ` jakub 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-114687-4-j0okHIjerH@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).