Tamar Christina writes:
> Hi Richard,
>
> The 02/11/2019 18:22, Richard Sandiford wrote:
>> pollute the target-independent namespace). Then we can use something like:
>>
>> expand_operand ops[3];
>> create_output_operand (&ops[0], dest, mode);
>> create_input_operand (&ops[1], pred, GET_MO
Hi Richard,
The 02/11/2019 18:22, Richard Sandiford wrote:
> pollute the target-independent namespace). Then we can use something like:
>
> expand_operand ops[3];
> create_output_operand (&ops[0], dest, mode);
> create_input_operand (&ops[1], pred, GET_MODE (pred));
> create_input_opera
Tamar Christina writes:
> diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c
> index
> 5df5a8b78439e69705e62845a4d1f86166a01894..59f03e688e58c1aab37629555c7b3f19e5075935
> 100644
> --- a/gcc/config/aarch64/aarch64.c
> +++ b/gcc/config/aarch64/aarch64.c
> @@ -3414,6 +3414,14
Hi All,
On AArch64 aarch64_classify_address has a case for when it's non-strict
that will allow it to accept any byte offset from a reg when validating
an address in a given addressing mode.
This because reload would later make the address valid. SVE however requires
the address always be valid,
