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/112337] arm: ICE in arm_effective_regno when compiling for MVE Date: Fri, 10 Nov 2023 16:47:46 +0000 [thread overview] Message-ID: <bug-112337-4-UB6lvq9CYU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112337-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112337 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>: https://gcc.gnu.org/g:df66fa08578a28b3acc8bdb6257b68c245a6a0fa commit r14-5333-gdf66fa08578a28b3acc8bdb6257b68c245a6a0fa Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Fri Nov 10 11:14:46 2023 -0500 [IRA]: Check autoinc and memory address after temporary equivalence substitution My previous RA patches to take register equivalence into account do temporary register equivalence substitution to find out that the equivalence can be consumed by insns. The insn with the substitution is checked on validity using target-depended code. This code expects that autoinc operations work on register but this register can be substituted by equivalent memory. The patch fixes this problem. The patch also adds checking that the substitution can be consumed in memory address too. gcc/ChangeLog: PR target/112337 * ira-costs.cc: (validate_autoinc_and_mem_addr_p): New function. (equiv_can_be_consumed_p): Use it. gcc/testsuite/ChangeLog: PR target/112337 * gcc.target/arm/pr112337.c: New.
next prev parent reply other threads:[~2023-11-10 16:47 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-01 15:49 [Bug target/112337] New: arm: ICE in arm_effective_regno stammark at gcc dot gnu.org 2023-11-02 10:02 ` [Bug target/112337] arm: ICE in arm_effective_regno when compiling for MVE rguenth at gcc dot gnu.org 2023-11-02 15:04 ` stammark at gcc dot gnu.org 2023-11-02 15:05 ` stammark at gcc dot gnu.org 2023-11-02 15:05 ` stammark at gcc dot gnu.org 2023-11-07 16:11 ` saurabh.jha at arm dot com 2023-11-07 16:49 ` pinskia at gcc dot gnu.org 2023-11-07 17:10 ` acoplan at gcc dot gnu.org 2023-11-08 12:41 ` vmakarov at gcc dot gnu.org 2023-11-08 12:50 ` acoplan at gcc dot gnu.org 2023-11-10 16:47 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-14 14:41 ` saurabh.jha at arm dot com 2023-11-14 14:50 ` cvs-commit at gcc dot gnu.org 2024-01-18 13:21 ` adhemerval.zanella at linaro dot org 2024-01-18 18:01 ` clyon at gcc dot gnu.org 2024-01-19 9:12 ` saurabh.jha at arm dot com 2024-02-05 9:30 ` saurabh.jha at arm dot com 2024-03-05 15:27 ` rearnsha at gcc dot gnu.org 2024-03-05 15:29 ` cvs-commit at gcc dot gnu.org 2024-03-05 15:35 ` 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-112337-4-UB6lvq9CYU@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).