New patch: [AArch64] [BE] [1/2] Make large opaque integer modes endianness-safe.
Christophe Lyon
christophe.lyon@linaro.org
Sun Jan 25 23:07:00 GMT 2015
On 17 December 2014 at 18:02, Tejas Belagod <tejas.belagod@arm.com> wrote:
> On 17/12/14 16:46, Marcus Shawcroft wrote:
>>
>> On 17 December 2014 at 15:15, Tejas Belagod <tejas.belagod@arm.com> wrote:
>>
>>>> It isn;t clear to me how far through the various BE patches we need to
>>>> get before 59810 is actually resolved?
>>>
>>>
>>>
>>> David's 2 patches
>>>
>>> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg01431.html
>>> https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01099.html
>>>
>>> and Alan's 2 patches:
>>>
>>> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02797.html
>>
>>
>> OK, thanks, my understanding is that all of the above are now blocked
>> waiting some resolution on this patch to rtlanal.c:
>
>
> I believe so.
>
> Thanks,
> Tejas.
>
Hi,
If I'm not mistaken, this has been committed as r219959, and is
causing regressions on aarch64_be for several AdvSimd intrinsic tests:
vldX_lane, vtrn, vuzp, vzip, as well as vldN_1 and vstN_1
See:
http://abe.tcwglab.linaro.org/logs/validations/cross-validation/gcc/trunk/219959/report-build-info.html
These tests started passing at the previous commit (r219958) with the
other half of this patch.
I haven't looked at the details yet.
Christophe.
>>
>>> https://gcc.gnu.org/ml/gcc-patches/2014-12/msg01087.html
>>
>>
>> /Marcus
>>
>
>
More information about the Gcc-patches
mailing list