search for: vceq_s8

...> I'll be sending patches to NEON.td for all ambiguities I find... Wait a minute.... VCEQ does not have a special polynomial version. There is only VCEQ.I8. What I said about support for polynomial types in Clang is still true, but for this particular case, there is no difference between vceq_s8, vceq_u8, and vceq_p8 (aside from the types of the intrinsic arguments).

On 27 September 2010 23:03, Bob Wilson <bob.wilson at apple.com> wrote: > Can you clarify ARM's position on those structure types?  It sounds like you are advocating that we get rid of them.  The only reason we've been using them in llvm-gcc and clang is for compatibility for ARM's specifications and with ARM's RVCT compiler.  If ARM does not care about those things,

...ally 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 - | grep vceq .globl vceq .type vceq,%function vceq: vceq.i8 d0, d1, d0 vce...

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

...ere'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 - | grep vceq > .globl vceq > .t...

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

...ctors are implemented in LLVM, there is no other way... maybe not. > Wait a minute....  VCEQ does not have a special polynomial version.  There is only VCEQ.I8.  What I said about support for polynomial types in Clang is still true, but for this particular case, there is no difference between vceq_s8, vceq_u8, and vceq_p8 (aside from the types of the intrinsic arguments). Sorry, bad example... (and wrong copy&past test generation) ;) -- cheers, --renato http://systemcall.org/ Reclaim your digital rights, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm