From: Richard Sandiford <richard.sandiford@arm.com>
To: Joey Ye <joey.ye.cc@gmail.com>
Cc: kyrylo.tkachov@foss.arm.com, "Bin.Cheng" <amker.cheng@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
James Greenhalgh <James.Greenhalgh@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Jeff Law <law@redhat.com>
Subject: Re: [PATCH AArch64]Fix test failure for pr84682-2.c
Date: Wed, 29 Aug 2018 18:47:00 -0000 [thread overview]
Message-ID: <87tvndm2lz.fsf@arm.com> (raw)
In-Reply-To: <CAL0py25M1h1onsO4swSHrjLtcoR_QaeefGQjqWqEtC3iD3ZtsA@mail.gmail.com> (Joey Ye's message of "Wed, 29 Aug 2018 16:50:08 +0100")
Joey Ye <joey.ye.cc@gmail.com> writes:
> diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c
> index 07c55b1..9e965ab 100644
> --- a/gcc/config/aarch64/aarch64.c
> +++ b/gcc/config/aarch64/aarch64.c
> @@ -5674,9 +5674,6 @@ aarch64_classify_address (struct aarch64_address_info *info,
> && (code != POST_INC && code != REG))
> return false;
>
> - gcc_checking_assert (GET_MODE (x) == VOIDmode
> - || SCALAR_INT_MODE_P (GET_MODE (x)));
> -
> switch (code)
> {
> case REG:
> diff --git a/gcc/recog.c b/gcc/recog.c
> index 0a8fa2c..510aba2 100644
> --- a/gcc/recog.c
> +++ b/gcc/recog.c
> @@ -1070,6 +1070,11 @@ general_operand (rtx op, machine_mode mode)
> int
> address_operand (rtx op, machine_mode mode)
> {
> + /* Wrong mode for an address expr. */
> + if (GET_MODE (op) != VOIDmode
> + && ! SCALAR_INT_MODE_P (GET_MODE (op)))
> + return false;
> +
> return memory_address_p (mode, op);
> }
>
The address_operand part is OK, thanks.
I think we should keep the assert in aarch64_classify_address, since
IMO it's a bug for anything else to reach that point.
Richard
next prev parent reply other threads:[~2018-08-29 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 11:43 Bin Cheng
2018-03-16 11:53 ` Kyrill Tkachov
2018-03-17 9:20 ` Richard Sandiford
2018-03-22 11:11 ` Bin.Cheng
2018-04-24 15:14 ` Bin.Cheng
2018-05-16 8:37 ` Kyrill Tkachov
2018-08-29 15:50 ` Joey Ye
2018-08-29 18:47 ` Richard Sandiford [this message]
2018-08-30 1:02 ` Bin.Cheng
2018-08-30 10:21 ` Joey Ye
2018-08-30 10:28 ` Joey Ye
2018-08-30 12:24 ` Richard Sandiford
2018-12-12 11:29 ` Richard Earnshaw (lists)
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=87tvndm2lz.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=James.Greenhalgh@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=amker.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joey.ye.cc@gmail.com \
--cc=kyrylo.tkachov@foss.arm.com \
--cc=law@redhat.com \
/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).