James,
This is a follow-up to https://gcc.gnu.org/ml/gcc/2017-03/msg00109.html
where you said:
| Hi Ashwin,
|
| Thanks for the question. ARM has defined a vector function ABI, based
| on the Vector Function ABI Specification you linked below, which
| is designed to be suitable for both the Adva
On Fri, 2018-02-09 at 17:58 +, Richard Sandiford wrote:
>
> OK, so is this in aarch64_builtin_vectorized_function? to_constant
> isn't valid there because the code isn't specific to Advanced SIMD.
> The way to check for V2xx is:
>
> known_eq (TYPE_VECTOR_SUBPARTS (...), 2U)
>
> Thanks,
>
Steve Ellcey writes:
> On Fri, 2018-02-09 at 17:15 +, Richard Sandiford wrote:
>>
>>
>> If the code you're adding is inherently specific to Advanced SIMD
>> (not sure, but guessing yes based on this being aarch64-builtins.c)
>> then like Kugan says, using to_constant is OK.
>>
>> Which code
On Fri, 2018-02-09 at 17:15 +, Richard Sandiford wrote:
>
>
> If the code you're adding is inherently specific to Advanced SIMD
> (not sure, but guessing yes based on this being aarch64-builtins.c)
> then like Kugan says, using to_constant is OK.
>
> Which code are you copying over?
>
> Tha
Steve Ellcey writes:
> I have a question about the poly_uint64 type and the TYPE_VECTOR_SUBPARTS
> macro. I am trying to copy some code from i386.c into my aarch64 build
> that is basically:
>
> int n;
> n = TYPE_VECTOR_SUBPARTS (type_out);
>
> And it is not compiling for me, I get:
>
> /home/sel
