public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia 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: Wed, 24 Jan 2024 00:53:29 +0000 [thread overview] Message-ID: <bug-113510-4-9b7BAYvgMM@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 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2024-01-24 Status|UNCONFIRMED |NEW --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Yes the peephole2 in thumb1.md looks wrong: ``` ;; Reloading and elimination of the frame pointer can ;; sometimes cause this optimization to be missed. (define_peephole2 [(set (match_operand:SI 0 "arm_general_register_operand" "") (match_operand:SI 1 "const_int_operand" "")) (set (match_dup 0) (plus:SI (match_dup 0) (reg:SI SP_REGNUM)))] "TARGET_THUMB1 && UINTVAL (operands[1]) < 1024 && (UINTVAL (operands[1]) & 3) == 0" [(set (match_dup 0) (plus:SI (reg:SI SP_REGNUM) (match_dup 1)))] "" ) ``` Confirmed.
next prev parent reply other threads:[~2024-01-24 0:53 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 [this message] 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 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-9b7BAYvgMM@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).