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/97528] [9/10 Regression] ICE in decompose_automod_address, at rtlanal.c:6298 (arm-linux-gnueabihf)
Date: Wed, 25 Nov 2020 11:56:51 +0000 [thread overview]
Message-ID: <bug-97528-4-zRKW9sO3bK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97528-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97528
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:05a3ab76e03ec6cff0bafb8495387b3a186785cc
commit r10-9077-g05a3ab76e03ec6cff0bafb8495387b3a186785cc
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Nov 20 12:26:58 2020 +0100
arm: Fix up neon_vector_mem_operand [PR97528]
The documentation for POST_MODIFY says:
Currently, the compiler can only handle second operands of the
form (plus (reg) (reg)) and (plus (reg) (const_int)), where
the first operand of the PLUS has to be the same register as
the first operand of the *_MODIFY.
The following testcase ICEs, because combine just attempts to simplify
things and ends up with
(post_modify (reg1) (plus (mult (reg2) (const_int 4)) (reg1))
but the target predicates accept it, because they only verify
that POST_MODIFY's second operand is PLUS and the second operand
of the PLUS is a REG.
The following patch fixes this by performing further verification that
the POST_MODIFY is in the form it should be.
2020-11-20 Jakub Jelinek <jakub@redhat.com>
PR target/97528
* config/arm/arm.c (neon_vector_mem_operand): For POST_MODIFY,
require
first POST_MODIFY operand is a REG and is equal to the first
operand
of PLUS.
* gcc.target/arm/pr97528.c: New test.
(cherry picked from commit 410b8f6f41920dad200cd709f9f3de8b840a995c)
next prev parent reply other threads:[~2020-11-25 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 11:42 [Bug target/97528] New: [10/11 " doko at debian dot org
2020-10-22 11:52 ` [Bug target/97528] " rguenth at gcc dot gnu.org
2020-10-23 11:25 ` ktkachov at gcc dot gnu.org
2020-11-18 16:12 ` [Bug target/97528] [9/10/11 " jakub at gcc dot gnu.org
2020-11-18 16:14 ` jakub at gcc dot gnu.org
2020-11-20 11:27 ` cvs-commit at gcc dot gnu.org
2020-11-20 11:42 ` [Bug target/97528] [9/10 " jakub at gcc dot gnu.org
2020-11-25 11:56 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-01 13:28 ` avieira at gcc dot gnu.org
2021-02-01 13:30 ` ktkachov at gcc dot gnu.org
2021-02-01 13:36 ` jakub at gcc dot gnu.org
2021-02-03 10:03 ` cvs-commit at gcc dot gnu.org
2021-02-03 18:32 ` cvs-commit at gcc dot gnu.org
2021-02-03 18:33 ` avieira at gcc dot gnu.org
2021-02-03 18:37 ` jakub 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-97528-4-zRKW9sO3bK@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).