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 target/112845] [11/12/13 Regression] ICE: in extract_insn, at recog.cc:2804 with -Os -fcf-protection -c since r8-3504 Date: Tue, 05 Dec 2023 12:19:31 +0000 [thread overview] Message-ID: <bug-112845-4-N9PlAUlWms@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112845-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112845 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[11/12/13/14 Regression] |[11/12/13 Regression] ICE: |ICE: in extract_insn, at |in extract_insn, at |recog.cc:2804 with -Os |recog.cc:2804 with -Os |-fcf-protection -c since |-fcf-protection -c since |r8-3504 |r8-3504 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Fixed on the trunk so far.
next prev parent reply other threads:[~2023-12-05 12:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-04 14:04 [Bug target/112845] New: ICE: in extract_insn, at recog.cc:2804 with -Os -fcf-protection -c iamanonymous.cs at gmail dot com 2023-12-04 15:35 ` [Bug target/112845] [11/12/13/14 Regression] ICE: in extract_insn, at recog.cc:2804 with -Os -fcf-protection -c since r8-3504 jakub at gcc dot gnu.org 2023-12-04 15:38 ` jakub at gcc dot gnu.org 2023-12-04 15:38 ` jakub at gcc dot gnu.org 2023-12-05 12:18 ` cvs-commit at gcc dot gnu.org 2023-12-05 12:19 ` jakub at gcc dot gnu.org [this message] 2023-12-05 16:33 ` [Bug target/112845] [11/12/13 " cvs-commit at gcc dot gnu.org 2023-12-05 17:02 ` [Bug target/112845] [11/12 " jakub at gcc dot gnu.org 2023-12-16 0:38 ` cvs-commit at gcc dot gnu.org 2023-12-17 13:55 ` cvs-commit 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-112845-4-N9PlAUlWms@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).