Displaying 3 results from an estimated 3 matches for "neon_intrinsic1".
Did you mean:
neon_intrinsics
2013 Oct 02
2
[LLVMdev] Implementing the ARM NEON Intrinsics for PowerPC
...using Clang as the frontend? If so, my recommendation would be to start by creating a header file that implements the NEON intrinsics in terms of generic functionality and the Altivec ones. The header file would need to look kind of like this:
#if defined(__powerpc__) || defined(__ppc__)
#define neon_intrinsic1 ppc_neon_intrinsic1
static __inline__ vec_type __attribute__((__always_inline__, __nodebug__))
ppc_neon_intrinsic1(vec_type a1, vec_type a2) {
...
}
...
#endif
If you look in tools/clang/lib/Headers you'll see lots of example intrinsics header files, and if you look in your build directory...
2013 Oct 02
0
[LLVMdev] Implementing the ARM NEON Intrinsics for PowerPC
On 2 October 2013 12:17, Renato Golin <renato.golin at linaro.org> wrote:
> On 2 October 2013 10:12, Steven Newbury <steve at snewbury.org.uk> wrote:
>
>> How does this make any sense?
>>
>
> I have to agree with you that this doesn't make much sense, but there is a
> case where you would want something like that: when the original source
> uses NEON
2013 Oct 02
3
[LLVMdev] Implementing the ARM NEON Intrinsics for PowerPC
On 2 October 2013 10:12, Steven Newbury <steve at snewbury.org.uk> wrote:
> How does this make any sense?
>
I have to agree with you that this doesn't make much sense, but there is a
case where you would want something like that: when the original source
uses NEON intrinsics, and there is no alternative in AltiVec, AVX or even
plain C.
We encourage people to use NEON intrinsics,