public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113720] [14 Regression] internal compiler error: in extract_insn, at recog.cc:2812 targeting alpha-linux-gnu Date: Fri, 02 Feb 2024 18:38:51 +0000 [thread overview] Message-ID: <bug-113720-4-A8m3nDHoR3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113720-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113720 Roger Sayle <roger at nextmovesoftware dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger at nextmovesoftware dot com --- Comment #3 from Roger Sayle <roger at nextmovesoftware dot com> --- Sorry for the inconvenience. alpha.md's define_expand that creates RTL that contains a MULT with operands of different modes looks highly suspicious. Uros' patch to use the (relatively recently added) UMUL_HIGHPART rtx_code is certainly a step in the right direction.
next prev parent reply other threads:[~2024-02-02 18:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-02 13:18 [Bug target/113720] New: " doko at gcc dot gnu.org 2024-02-02 14:01 ` [Bug target/113720] " ubizjak at gmail dot com 2024-02-02 14:55 ` jsm28 at gcc dot gnu.org 2024-02-02 18:38 ` roger at nextmovesoftware dot com [this message] 2024-02-03 9:28 ` doko at gcc dot gnu.org 2024-02-03 9:54 ` ubizjak at gmail dot com 2024-02-03 13:20 ` doko at gcc dot gnu.org 2024-02-12 10:36 ` jakub at gcc dot gnu.org 2024-03-03 19:42 ` cvs-commit at gcc dot gnu.org 2024-03-03 19:44 ` ubizjak at gmail dot com
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-113720-4-A8m3nDHoR3@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).