public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108783] [13 Regression] ICE: verify_flow_info failed (error: returns_twice call is not first in basic block 3) Date: Wed, 15 Feb 2023 11:26:16 +0000 [thread overview] Message-ID: <bug-108783-4-feUNx5xsRX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108783-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108783 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Though, the optimization that does this has been added in r0-99848-g844381e5bc6eb515df838279 for PR28685.
next prev parent reply other threads:[~2023-02-15 11:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-14 3:44 [Bug tree-optimization/108783] New: " asolokha at gmx dot com 2023-02-14 7:13 ` [Bug tree-optimization/108783] " rguenth at gcc dot gnu.org 2023-02-15 11:16 ` jakub at gcc dot gnu.org 2023-02-15 11:26 ` jakub at gcc dot gnu.org [this message] 2023-02-15 11:45 ` jakub at gcc dot gnu.org 2023-02-15 12:38 ` jakub at gcc dot gnu.org 2023-02-16 9:42 ` cvs-commit at gcc dot gnu.org 2023-02-16 9:42 ` 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-108783-4-feUNx5xsRX@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).