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 middle-end/110294] [10/11 Regression] Segmentation fault with '-O3 -fno-dce -fno-toplevel-reorder -fno-tree-dce -fno-tree-pta -fno-tree-sink -ftoplevel-reorder' Date: Mon, 19 Jun 2023 06:58:03 +0000 [thread overview] Message-ID: <bug-110294-4-H1zctHIVGM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110294-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110294 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |10.1.0, 11.1.0, 11.3.0 Known to work| |13.1.0 Summary|Segmentation fault with |[10/11 Regression] |'-O3 -fno-dce |Segmentation fault with |-fno-toplevel-reorder |'-O3 -fno-dce |-fno-tree-dce -fno-tree-pta |-fno-toplevel-reorder |-fno-tree-sink |-fno-tree-dce -fno-tree-pta |-ftoplevel-reorder' |-fno-tree-sink | |-ftoplevel-reorder' Target Milestone|--- |10.5
next prev parent reply other threads:[~2023-06-19 6:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-17 4:49 [Bug c/110294] New: " 19373742 at buaa dot edu.cn 2023-06-17 4:49 ` [Bug c/110294] " 19373742 at buaa dot edu.cn 2023-06-17 6:50 ` xry111 at gcc dot gnu.org 2023-06-19 6:58 ` rguenth at gcc dot gnu.org [this message] 2023-06-30 9:08 ` [Bug middle-end/110294] [10/11 Regression] " 19373742 at buaa dot edu.cn 2023-06-30 9:31 ` xry111 at gcc dot gnu.org 2023-07-07 10:45 ` [Bug middle-end/110294] [11 " rguenth at gcc dot gnu.org 2024-01-10 15:23 ` jamborm at gcc dot gnu.org 2024-01-11 1:05 ` pinskia 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-110294-4-H1zctHIVGM@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).