Displaying 5 results from an estimated 5 matches for "int8x8_t".
2011 Nov 23
4
[LLVMdev] arm neon intrinsics cross compile error on windows system
...0rc4/bin/../lib/clang/3.0/include\arm_neon.h:355:10:
error: invalid conversion between vector type
'__attribute__((__vector_size__(16 * sizeof(signed char)))) signed char'
and integer type 'int32x4_t' (aka 'long') of different size
return (int32x4_t)__builtin_neon_vmovl_v((int8x8_t)__a, 18); }
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
d:/llvm_projects/llvm-3.0rc4/bin/../lib/clang/3.0/include\arm_neon.h:357:44:
error: invalid conversion between vector type 'int8x8_t' and integer type
'int32x2_t' (aka 'long') of different size
retur...
2010 Sep 27
2
[LLVMdev] Vectors in structures
...een uint8x8 and int8x8 is done via 'nsw' (which,
unless it's really generating a trap value, it's a misleading tag),
but there's nothing that will flag this type as poly8x8.
When I try to compile this with Clang:
=== comp.c ===
#define __ARM_NEON__
#include <arm_neon.h>
int8x8_t i8d;
uint8x8_t u8d;
poly8x8_t p8d;
void vceq() {
u8d = vceq_s8(i8d, i8d);
u8d = vceq_p8(p8d, p8d);
}
=== end ===
It generates exactly the same instruction for both calls:
$ clang -ccc-host-triple armv7a-none-eabi -ccc-gcc-name
arm-none-eabi-gcc -mfloat-abi=hard -w -S comp.c -o - | g...
2010 Sep 27
0
[LLVMdev] Vectors in structures
On Sep 27, 2010, at 2:58 AM, Renato Golin wrote:
> On 22 September 2010 03:43, Bob Wilson <bob.wilson at apple.com> wrote:
>> But regardless they are still structures, right? What does it mean for them to map onto other types? Is the parser supposed to treat them as if they _were_ those other types? If so, I think you need to define a type system for those fundamental vector
2010 Sep 27
0
[LLVMdev] Vectors in structures
...which,
> unless it's really generating a trap value, it's a misleading tag),
> but there's nothing that will flag this type as poly8x8.
>
> When I try to compile this with Clang:
>
> === comp.c ===
> #define __ARM_NEON__
> #include <arm_neon.h>
>
> int8x8_t i8d;
> uint8x8_t u8d;
> poly8x8_t p8d;
>
> void vceq() {
> u8d = vceq_s8(i8d, i8d);
> u8d = vceq_p8(p8d, p8d);
> }
> === end ===
>
> It generates exactly the same instruction for both calls:
>
> $ clang -ccc-host-triple armv7a-none-eabi -ccc-gcc-nam...
2010 Sep 27
2
[LLVMdev] Vectors in structures
On 22 September 2010 03:43, Bob Wilson <bob.wilson at apple.com> wrote:
> But regardless they are still structures, right? What does it mean for them to map onto other types? Is the parser supposed to treat them as if they _were_ those other types? If so, I think you need to define a type system for those fundamental vector types. I had read those statements to say something about the