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 rtl-optimization/110079] [10/11/12/13/14 Regression] ICE with -freorder-blocks-and-partition and inline-asm goto Date: Thu, 01 Jun 2023 13:13:29 +0000 [thread overview] Message-ID: <bug-110079-4-gqrf6FM3al@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110079-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110079 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |10.4.0, 12.2.0, 13.1.0, | |8.2.0, 9.5.0 Target Milestone|--- |10.5 Known to work| |6.4.0, 7.3.0, 7.5.0 Keywords| |ice-on-valid-code Target| |aarch64*-*-* riscv*-*-* Summary|ICE with |[10/11/12/13/14 Regression] |-freorder-blocks-and-partit |ICE with |ion and inline-asm goto |-freorder-blocks-and-partit | |ion and inline-asm goto
next prev parent reply other threads:[~2023-06-01 13:13 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-01 12:58 [Bug rtl-optimization/110079] New: ICE with -freorder-blocks-and-partition yancheng.li at foxmail dot com 2023-06-01 13:13 ` pinskia at gcc dot gnu.org [this message] 2023-06-01 13:14 ` [Bug rtl-optimization/110079] [10/11/12/13/14 Regression] ICE with -freorder-blocks-and-partition and inline-asm goto pinskia at gcc dot gnu.org 2023-06-02 11:48 ` yancheng.li at foxmail dot com 2023-07-07 10:45 ` [Bug rtl-optimization/110079] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-01-12 14:06 ` rguenth at gcc dot gnu.org 2024-03-06 18:01 ` jakub at gcc dot gnu.org 2024-03-07 9:08 ` cvs-commit at gcc dot gnu.org 2024-03-07 9:37 ` [Bug rtl-optimization/110079] [11/12/13 " jakub at gcc dot gnu.org 2024-03-15 23:29 ` cvs-commit at gcc dot gnu.org 2024-03-18 14:41 ` [Bug rtl-optimization/110079] [11/12 " 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-110079-4-gqrf6FM3al@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).