public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/116413] [LRA] [M68K] ICE: unrecognized insn in lra_set_insn_recog_data, at lra.cc:1036
Date: Mon, 19 Aug 2024 13:36:59 +0000	[thread overview]
Message-ID: <bug-116413-4-ZbIvEKHdgB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-116413-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116413

Michael Matz <matz at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matz at gcc dot gnu.org

--- Comment #8 from Michael Matz <matz at gcc dot gnu.org> ---
Yeah, reload doesn't expect ASHIFTs within operands here.  The below would fix
that:

diff --git a/gcc/final.cc b/gcc/final.cc
index eb9e065d9f0..5d911586de5 100644
--- a/gcc/final.cc
+++ b/gcc/final.cc
@@ -3146,6 +3146,7 @@ walk_alter_subreg (rtx *xp, bool *changed)
     case PLUS:
     case MULT:
     case AND:
+    case ASHIFT:
       XEXP (x, 0) = walk_alter_subreg (&XEXP (x, 0), changed);
       XEXP (x, 1) = walk_alter_subreg (&XEXP (x, 1), changed);
       break;

  parent reply	other threads:[~2024-08-19 13:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  7:56 [Bug target/116413] New: " schwab@linux-m68k.org
2024-08-19  8:01 ` [Bug target/116413] " schwab@linux-m68k.org
2024-08-19  8:25 ` schwab@linux-m68k.org
2024-08-19  9:42 ` schwab@linux-m68k.org
2024-08-19 12:59 ` schwab@linux-m68k.org
2024-08-19 13:02 ` schwab@linux-m68k.org
2024-08-19 13:16 ` schwab@linux-m68k.org
2024-08-19 13:31 ` schwab@linux-m68k.org
2024-08-19 13:36 ` matz at gcc dot gnu.org [this message]
2024-08-20  9:00 ` rsandifo at gcc dot gnu.org
2024-08-21  8:34 ` schwab@linux-m68k.org
2024-08-21  8:56 ` rsandifo at gcc dot gnu.org
2024-08-21  9:13 ` schwab@linux-m68k.org
2024-08-21  9:18 ` schwab@linux-m68k.org
2024-08-21 11:16 ` rsandifo at gcc dot gnu.org
2024-08-21 12:16 ` schwab@linux-m68k.org
2024-08-21 12:36 ` schwab@linux-m68k.org
2024-08-21 12:44 ` rsandifo at gcc dot gnu.org
2024-08-21 13:47 ` matz at gcc dot gnu.org
2024-08-27  8:48 ` cvs-commit at gcc dot gnu.org
2024-08-27 13:35 ` cvs-commit at gcc dot gnu.org
2024-08-27 20:22 ` cvs-commit at gcc dot gnu.org
2024-08-27 20:23 ` schwab@linux-m68k.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-116413-4-ZbIvEKHdgB@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: link
Be 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).