search for: fmull

Displaying 5 results from an estimated 5 matches for "fmull".

Did you mean: fmul
2013 Feb 08
0
[LLVMdev] Is there any llvm neon intrinsic that maps to vmla.f32 instruction ?
...e for that ?**** > > Hi Sebastien, LLVM doesn't use intrinsics when there is a clear way of representing the same thing on standard IR. In the case of VMLA, it is generated from a pattern: %mul = mul <N x type> %a, %b %sum = add <N x type> %mul, %c So, if you generate FAdd(FMull(a, b), c), you'll probably get an FMLA. It's not common, but also not impossible that the two instructions will be reordered, or even removed, so you need to make sure the intermediate result is not used (or it'll probably use VMUL/VADD) and the final result is used (or it'll be r...
2013 Feb 08
2
[LLVMdev] Is there any llvm neon intrinsic that maps to vmla.f32 instruction ?
Hi all, Everything is in the tile, I would like to enforce generation of vmla.f32 instruction for scalar operations on cortex-a9, so is there a LLMV neon intrinsic available for that ? Thanks for your answers Best Regards Seb -------------- next part -------------- An HTML attachment was scrubbed... URL:
2013 Feb 08
2
[LLVMdev] Is there any llvm neon intrinsic that maps to vmla.f32 instruction ?
...nsic available for that ? Hi Sebastien, LLVM doesn't use intrinsics when there is a clear way of representing the same thing on standard IR. In the case of VMLA, it is generated from a pattern: %mul = mul <N x type> %a, %b %sum = add <N x type> %mul, %c So, if you generate FAdd(FMull(a, b), c), you'll probably get an FMLA. It's not common, but also not impossible that the two instructions will be reordered, or even removed, so you need to make sure the intermediate result is not used (or it'll probably use VMUL/VADD) and the final result is used (or it'll be r...
2007 Apr 18
4
[patch 0/4] Clean up asm/bugs.h, identify_cpu() and update COMPAT_VDSO
Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --
2007 Apr 18
4
[patch 0/4] Clean up asm/bugs.h, identify_cpu() and update COMPAT_VDSO
Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --