From: Richard Sandiford <richard.sandiford@linaro.org>
To: Chung-Lin Tang <cltang@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <rearnsha@arm.com>
Subject: Re: [patch, ARM] PR48250, rehaul arm_legitimize_reload_address()
Date: Wed, 20 Apr 2011 14:00:00 -0000 [thread overview]
Message-ID: <g4k4ep5a40.fsf@linaro.org> (raw)
In-Reply-To: <4D9EBEC8.2020807@codesourcery.com> (Chung-Lin Tang's message of "Fri, 08 Apr 2011 15:52:40 +0800")
Hi Chung-Lin,
I'm seeing an ICE with this patch, specifically;
Chung-Lin Tang <cltang@codesourcery.com> writes:
> + if (coproc_p)
> + low = SIGN_MAG_LOW_ADDR_BITS (val, 10);
We generate:
Reload 1: reload_out (V4SI) = (mem/c:V4SI (plus:SI (plus:SI (reg/f:SI 11 fp)
(const_int -6144 [0xffffffffffffe800]))
(const_int 1020 [0x3fc])) [43 %sfp+-5024 S16 A64])
but 1020 isn't a legitimate offset for V4SI:
/* For quad modes, we restrict the constant offset to be slightly less
than what the instruction format permits. We do this because for
quad mode moves, we will actually decompose them into two separate
double-mode reads or writes. INDEX must therefore be a valid
(double-mode) offset and so should INDEX+8. */
if (TARGET_NEON && VALID_NEON_QREG_MODE (mode))
return (code == CONST_INT
&& INTVAL (index) < 1016
&& INTVAL (index) > -1024
&& (INTVAL (index) & 3) == 0);
A simple "fix" would be to use 9 instead of 10, but something a little
more subtle might be preferred :-)
Richard
next prev parent reply other threads:[~2011-04-20 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 7:53 Chung-Lin Tang
2011-04-11 10:54 ` Richard Earnshaw
2011-04-20 14:00 ` Richard Sandiford [this message]
2011-04-20 15:19 ` Chung-Lin Tang
2011-04-20 15:23 ` Richard Earnshaw
2011-04-20 15:37 ` Chung-Lin Tang
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=g4k4ep5a40.fsf@linaro.org \
--to=richard.sandiford@linaro.org \
--cc=cltang@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rearnsha@arm.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).