public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103627] ICE: in extract_insn, at recog.c:2769 (error: unrecognizable insn) Date: Fri, 10 Dec 2021 10:40:44 +0000 [thread overview] Message-ID: <bug-103627-4-Fi7DY88wZq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103627-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103627 --- Comment #2 from Kewen Lin <linkw at gcc dot gnu.org> --- Confirmed. But even if I reverted my previous commit r12-5590 which introduced this test case (from PR102347) into testsuites, this ICE still exists. So it's not a regression related to the commit but a latent issue. I can see the same ICE on BE with -m32 -mcpu=powerpc (or -mcpu=powerpc64).
next prev parent reply other threads:[~2021-12-10 10:40 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-09 11:08 [Bug target/103627] New: " asolokha at gmx dot com 2021-12-10 10:05 ` [Bug target/103627] " linkw at gcc dot gnu.org 2021-12-10 10:40 ` linkw at gcc dot gnu.org [this message] 2021-12-20 5:20 ` linkw at gcc dot gnu.org 2021-12-20 5:29 ` linkw at gcc dot gnu.org 2022-02-07 5:48 ` cvs-commit at gcc dot gnu.org 2022-02-07 5:48 ` cvs-commit at gcc dot gnu.org 2022-02-15 7:26 ` asolokha at gmx dot com 2022-02-15 9:50 ` cvs-commit at gcc dot gnu.org 2022-02-15 9:50 ` cvs-commit at gcc dot gnu.org 2022-02-15 9:51 ` cvs-commit at gcc dot gnu.org 2022-02-15 9:51 ` cvs-commit at gcc dot gnu.org 2022-02-15 9:53 ` linkw 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-103627-4-Fi7DY88wZq@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).