llvm dev - May 2011 - [LLVMdev] Does the OCaml binding include intrinsic support?

I can't seem to find reference to intrinsics, beyond the is_intrinsic
function.

I am building a backend which needs to perform some target-specific
code-generation (for SSE, AVX, and NEON), and intrinsics are the
standard path in the C++ API.

On Fri, May 13, 2011 at 5:18 PM, Jonathan Ragan-Kelley <jrk at
csail.mit.edu>wrote:
> I can't seem to find reference to intrinsics, beyond the is_intrinsic
> function.
>
> I am building a backend which needs to perform some target-specific
> code-generation (for SSE, AVX, and NEON), and intrinsics are the
> standard path in the C++ API.
>
What happens if you just build a call to a function with the same name as
the intrinsic you want?  I believe that should work.

> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>


-- 

Thanks,

Justin Holewinski
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20110514/e367c8c4/attachment.html>

Indeed, it would appear that I am a moron and that this obvious route works just
fine. I was confounded by the richer support for using intrinsics in the C++
interface, and some corresponding features in some 3rd party bindings (llvm-py,
in particular), but this works exactly as I should have expected from the .ll
assembly form.

I documented the results for a simple SSE test with an example on SO:

 
http://stackoverflow.com/questions/5997881/does-the-llvm-ocaml-binding-include-intrinsic-support

Thanks.


On May 14, 2011, at 10:36 AM, Justin Holewinski wrote:
> On Fri, May 13, 2011 at 5:18 PM, Jonathan Ragan-Kelley <jrk at
csail.mit.edu> wrote:
> I can't seem to find reference to intrinsics, beyond the is_intrinsic
function.
> 
> I am building a backend which needs to perform some target-specific
> code-generation (for SSE, AVX, and NEON), and intrinsics are the
> standard path in the C++ API.
> 
> What happens if you just build a call to a function with the same name as
the intrinsic you want?  I believe that should work.