From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: James Greenhalgh <james.greenhalgh@arm.com>, gcc-patches@gcc.gnu.org
Cc: nd@arm.com, richard.earnshaw@arm.com,
ramana.radhakrishnan@arm.com, nickc@redhat.com
Subject: Re: [Patch ARM] Fix PR71778
Date: Fri, 16 Jun 2017 10:07:00 -0000 [thread overview]
Message-ID: <5943ADED.10706@foss.arm.com> (raw)
In-Reply-To: <1497604036-4653-1-git-send-email-james.greenhalgh@arm.com>
On 16/06/17 10:07, James Greenhalgh wrote:
> On Wed, Jun 14, 2017 at 11:21:30AM +0100, Kyrill Tkachov wrote:
>
> <...>
>
>> That movv2di expander is the one in vec-common.md that ends up calling
>> neon_make_constant. I wonder why const0_rtx passed its predicate check
>> (that would require a V2DImode vector of zeroes rather than a const0_rtx).
>> Perhaps the midend code at this point doesn't check the operand predicate.
>>
>> In the builtin expansion code that you quoted I wonder wonder if we could fail
>> more gracefully by returning CONST0_RTX (mode[argc]) to match the expected
>> mode of the operand (we've already emitted an error, so we shouldn't care
>> what RTL we emit as long as it doesn't cause an ICE).
> <...>
>
>> diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c
>> index e503891..b8d59c6 100644
>> --- a/gcc/config/arm/arm.c
>> +++ b/gcc/config/arm/arm.c
>> @@ -12124,6 +12124,11 @@ neon_make_constant (rtx vals)
>> if (n_const == n_elts)
>> const_vec = gen_rtx_CONST_VECTOR (mode, XVEC (vals, 0));
>> }
>> + else if (vals == const0_rtx)
>> + /* Something invalid, perhaps from expanding an intrinsic
>> + which requires a constant argument, where a variable argument
>> + was passed. */
>> + return const0_rtx;
>> else
>> gcc_unreachable ();
>>
>> I'm not a fan of this as the function has a precondition that its argument is
>> a PARALLEL or a CONST_VECTOR and special-casing const0_rtx breaks that. I'd
>> rather we tried fixing this closer to the error source. Can you try the
>> suggestion above instead please?
> Your suggestion doesn't quite work, but this is pretty close to it. Rather
> than try to guess at the correct mode for CONST0_RTX (we can't just use
> mode[argc] as that will get you the scalar mode), we can just return target
> directly. That will ensure we've given something valid back in the correct
> mode, even if it is not all that useful.
Yeah, that actually looks better.
> Bootstrapped on arm-none-linux-gnueabihf. OK?
Ok.
Thanks,
Kyrill
>
> Thanks,
> James
>
> ---
> gcc/
>
> 2017-06-15 James Greenhalgh <james.greenhalgh@arm.com>
>
> PR target/71778
> * config/arm/arm-builtins.c (arm_expand_builtin_args): Return TARGET
> if given a non-constant argument for an intrinsic which requires a
> constant.
>
> gcc/testsuite/
>
> 2017-06-15 James Greenhalgh <james.greenhalgh@arm.com>
>
> PR target/71778
> * gcc.target/arm/pr71778.c: New.
>
next prev parent reply other threads:[~2017-06-16 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 13:58 James Greenhalgh
2017-06-14 10:21 ` Kyrill Tkachov
2017-06-16 9:07 ` James Greenhalgh
2017-06-16 10:07 ` Kyrill Tkachov [this message]
2017-06-19 16:17 ` James Greenhalgh
2017-06-19 16:25 ` Kyrill Tkachov
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=5943ADED.10706@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=nd@arm.com \
--cc=nickc@redhat.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=richard.earnshaw@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).