On 1 February 2016 at 17:14, Kyrill Tkachov wrote:
> Indeed I see the new passes on armeb-none-eabi.
> However, the new FAILs that I see are ICEs, not just vectorisation failures,
> so they need to be looked at.
>
> The ICEs that I see are:
> FAIL: gcc.dg/torture/vshuf-v4hi.c -O2 (internal com
On 16/12/15 17:44, Charles Baylis wrote:
Hi
Hi Charles,
sorry for the delay on this one.
This patch addresses incorrect recognition of VEC_PERM_EXPRs as VUZP
and VZIP on armeb-* targets. It also fixes the definition of the
vuzpq_* and vzipq_* NEON intrinsics which use incorrect lane
specif
ping^2
On 13 January 2016 at 13:37, Charles Baylis wrote:
> ping
>
> On 16 December 2015 at 17:44, Charles Baylis
> wrote:
>> Hi
>>
>> This patch addresses incorrect recognition of VEC_PERM_EXPRs as VUZP
>> and VZIP on armeb-* targets. It also fixes the definition of the
>> vuzpq_* and vzipq_*
ping
On 16 December 2015 at 17:44, Charles Baylis wrote:
> Hi
>
> This patch addresses incorrect recognition of VEC_PERM_EXPRs as VUZP
> and VZIP on armeb-* targets. It also fixes the definition of the
> vuzpq_* and vzipq_* NEON intrinsics which use incorrect lane
> specifiers in the use of __bu
Hi
This patch addresses incorrect recognition of VEC_PERM_EXPRs as VUZP
and VZIP on armeb-* targets. It also fixes the definition of the
vuzpq_* and vzipq_* NEON intrinsics which use incorrect lane
specifiers in the use of __builtin_shuffle().
The problem with arm_neon.h can be seen by temporari
