On Thu, Feb 28, 2019 at 10:00 AM Robin Murphy wrote:
>
> On 26/02/2019 20:44, Nick Desaulniers wrote:
> > On Mon, Feb 25, 2019 at 11:19 PM Ard Biesheuvel
> > wrote:
> >>
> >> On Tue, 26 Feb 2019 at 05:03, wrote:
> >>>
> >>> Clang warns: vector initializers are not compatible with NEON
On 26/02/2019 20:44, Nick Desaulniers wrote:
On Mon, Feb 25, 2019 at 11:19 PM Ard Biesheuvel
wrote:
On Tue, 26 Feb 2019 at 05:03, wrote:
Clang warns: vector initializers are not compatible with NEON intrinsics
in big endian mode [-Wnonportable-vector-initialization]
While this is usually
On Mon, Feb 25, 2019 at 08:03:42PM -0800, ndesaulni...@google.com wrote:
> Clang warns: vector initializers are not compatible with NEON intrinsics
> in big endian mode [-Wnonportable-vector-initialization]
>
> While this is usually the case, it's not an issue for this case since
> we're
On Tue, 26 Feb 2019 at 21:44, Nick Desaulniers wrote:
>
> On Mon, Feb 25, 2019 at 11:19 PM Ard Biesheuvel
> wrote:
> >
> > On Tue, 26 Feb 2019 at 05:03, wrote:
> > >
> > > Clang warns: vector initializers are not compatible with NEON intrinsics
> > > in big endian mode
On Mon, Feb 25, 2019 at 11:19 PM Ard Biesheuvel
wrote:
>
> On Tue, 26 Feb 2019 at 05:03, wrote:
> >
> > Clang warns: vector initializers are not compatible with NEON intrinsics
> > in big endian mode [-Wnonportable-vector-initialization]
> >
> > While this is usually the case, it's not an issue
On Tue, 26 Feb 2019 at 05:03, wrote:
>
> Clang warns: vector initializers are not compatible with NEON intrinsics
> in big endian mode [-Wnonportable-vector-initialization]
>
> While this is usually the case, it's not an issue for this case since
> we're initializing the uint8x16_t (16x
Clang warns: vector initializers are not compatible with NEON intrinsics
in big endian mode [-Wnonportable-vector-initialization]
While this is usually the case, it's not an issue for this case since
we're initializing the uint8x16_t (16x uint8_t's) with the same value.
Instead, use vdupq_n_u8
7 matches
Mail list logo