> On 15 Nov 2024, at 12:05, Richard Biener wrote:
>
> External email: Use caution opening links or attachments
>
>
> On Fri, 15 Nov 2024, Jennifer Schmitz wrote:
>
>>
>>
>>> On 7 Nov 2024, at 13:47, Richard Biener wrote:
>>>
>>> External email: Use caution opening links or attachments
>>
On Fri, 15 Nov 2024, Jennifer Schmitz wrote:
>
>
> > On 7 Nov 2024, at 13:47, Richard Biener wrote:
> >
> > External email: Use caution opening links or attachments
> >
> >
> > On Tue, 5 Nov 2024, Jennifer Schmitz wrote:
> >
> >> We are working on a patch to improve the codegen for the foll
> On 7 Nov 2024, at 13:47, Richard Biener wrote:
>
> External email: Use caution opening links or attachments
>
>
> On Tue, 5 Nov 2024, Jennifer Schmitz wrote:
>
>> We are working on a patch to improve the codegen for the following test case:
>> uint64x2_t foo (uint64x2_t r) {
>>uint32x4
On Tue, 5 Nov 2024, Jennifer Schmitz wrote:
> We are working on a patch to improve the codegen for the following test case:
> uint64x2_t foo (uint64x2_t r) {
> uint32x4_t a = vreinterpretq_u32_u64 (r);
> uint32_t t;
> t = a[0]; a[0] = a[1]; a[1] = t;
> t = a[2]; a[2] = a[3]; a[3] =
We are working on a patch to improve the codegen for the following test case:
uint64x2_t foo (uint64x2_t r) {
uint32x4_t a = vreinterpretq_u32_u64 (r);
uint32_t t;
t = a[0]; a[0] = a[1]; a[1] = t;
t = a[2]; a[2] = a[3]; a[3] = t;
return vreinterpretq_u64_u32 (a);
}
that GCC curr
