public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113510] [14 Regression] [ARM Thumb] ICE in extract_constrain_insn with CPU cortex-m23
Date: Tue, 05 Mar 2024 17:35:25 +0000	[thread overview]
Message-ID: <bug-113510-4-2fOmUs03wN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113510-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Earnshaw <rearnsha@gcc.gnu.org>:

https://gcc.gnu.org/g:067a012bde15bfb62d9af309d9d524ebfe91b705

commit r14-9322-g067a012bde15bfb62d9af309d9d524ebfe91b705
Author: Richard Earnshaw <rearnsha@arm.com>
Date:   Tue Mar 5 17:21:43 2024 +0000

    arm: check for low register before applying peephole [PR113510]

    For thumb1, when using a peephole to fuse

            mov reg, #const
            add reg, reg, SP

    into

            add reg, SP, #const

    we must first check that reg is a low register, otherwise we will ICE
    when trying to recognize the resulting insn.

    gcc/ChangeLog:

            PR target/113510
            * config/arm/thumb1.md (peephole2 to fuse mov imm/add SP): Use
            low_register_operand.

  parent reply	other threads:[~2024-03-05 17:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 22:56 [Bug rtl-optimization/113510] New: " thiago.bauermann at linaro dot org
2024-01-19 22:58 ` [Bug rtl-optimization/113510] " thiago.bauermann at linaro dot org
2024-01-19 23:00 ` thiago.bauermann at linaro dot org
2024-01-20  8:24 ` [Bug target/113510] [14 Regression ARM " pinskia at gcc dot gnu.org
2024-01-23 20:44 ` [Bug target/113510] [14 Regression] [ARM " vmakarov at gcc dot gnu.org
2024-01-24  0:53 ` pinskia at gcc dot gnu.org
2024-01-24 13:00 ` rearnsha at gcc dot gnu.org
2024-03-05 17:31 ` rearnsha at gcc dot gnu.org
2024-03-05 17:35 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-05 17:37 ` rearnsha 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-113510-4-2fOmUs03wN@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).