public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115142] [14/15 Regression] Unrecognizable insn in extract_insn, at recog.cc:2812 with -ftree-ter Date: Sat, 18 May 2024 14:23:40 +0000 [thread overview] Message-ID: <bug-115142-4-a42DEg6f5w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115142-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115142 --- Comment #2 from Jeffrey A. Law <law at gcc dot gnu.org> --- So just one high level note. Nobody is ever going to do something like "-ftree-ter" without having one of the optimization levels on. It's an option combination that just doesn't make sense. But we still shouldn't trigger aborts, ICEs and such. I think this is a minor bug in the mem_shadd_or_shadd_rtx_p function. It probably should be verifying that the value being shifted is a REG. Testing a fix.
next prev parent reply other threads:[~2024-05-18 14:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-17 17:55 [Bug target/115142] New: " patrick at rivosinc dot com 2024-05-17 18:04 ` [Bug target/115142] " ewlu at rivosinc dot com 2024-05-18 14:23 ` law at gcc dot gnu.org [this message] 2024-05-18 21:30 ` law at gcc dot gnu.org 2024-05-18 21:30 ` law at gcc dot gnu.org 2024-05-19 15:57 ` cvs-commit at gcc dot gnu.org 2024-05-21 6:31 ` [Bug target/115142] [14 " rguenth at gcc dot gnu.org 2024-05-21 13:24 ` law 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-115142-4-a42DEg6f5w@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).