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/113221] [14 Regression][aarch64]ICE in extract_insn, at recog.cc:2812 since r14-6605-gc0911c6b357ba9 Date: Wed, 17 Jan 2024 22:03:58 +0000 [thread overview] Message-ID: <bug-113221-4-EDQD9hywzD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113221-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113221 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:7a8124e341aebcc544b4720e920b625f4ffe4e8a commit r14-8194-g7a8124e341aebcc544b4720e920b625f4ffe4e8a Author: Andrew Pinski <quic_apinski@quicinc.com> Date: Tue Jan 16 15:37:49 2024 -0800 aarch64: Fix aarch64_ldp_reg_operand predicate not to allow all subreg [PR113221] So the problem here is that aarch64_ldp_reg_operand will all subreg even subreg of lo_sum. When LRA tries to fix that up, all things break. So the fix is to change the check to only allow reg and subreg of regs. Note the tendancy here is to use register_operand but that checks the mode of the register but we need to allow a mismatch modes for this predicate for now. Built and tested for aarch64-linux-gnu with no regressions (Also tested with the LD/ST pair pass back on). PR target/113221 gcc/ChangeLog: * config/aarch64/predicates.md (aarch64_ldp_reg_operand): For subreg, only allow REG operands instead of allowing all. gcc/testsuite/ChangeLog: * gcc.c-torture/compile/pr113221-1.c: New test. Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
next prev parent reply other threads:[~2024-01-17 22:03 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-03 18:07 [Bug target/113221] New: " mjires at suse dot cz 2024-01-03 18:09 ` [Bug target/113221] " pinskia at gcc dot gnu.org 2024-01-03 18:13 ` pinskia at gcc dot gnu.org 2024-01-03 18:13 ` pinskia at gcc dot gnu.org 2024-01-03 18:19 ` pinskia at gcc dot gnu.org 2024-01-08 12:52 ` jakub at gcc dot gnu.org 2024-01-16 23:24 ` pinskia at gcc dot gnu.org 2024-01-16 23:31 ` pinskia at gcc dot gnu.org 2024-01-17 0:10 ` pinskia at gcc dot gnu.org 2024-01-17 3:38 ` pinskia at gcc dot gnu.org 2024-01-17 22:03 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-17 22:04 ` pinskia at gcc dot gnu.org 2024-01-18 15:26 ` acoplan 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-113221-4-EDQD9hywzD@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).