[llvm-dev] Generating SPIR

[Nicholas Wilson via llvm-dev]

SPIR-V is no problem.
see https://github.com/thewilsonator/llvm-target-spirv (a submodule of below)
and https://github.com/thewilsonator/llvm
they are kept reasonably up to date with trunk (API breakage compatible).

I do want to merge it into trunk, but I need to make it use LLVM intrinsics instead of mangled Itanium C++ with extensions.
This will hopefully happen (at least get in motion) at IWOCL.

Nic

On 19 Dec 2017, at 10:27 pm, Jakob Bornecrantz <wallbraker at gmail.com<mailto:wallbraker at gmail.com>> wrote:

That really should change, at least for SPIR-V.

Cheers, Jakob.

On Tue, Dec 19, 2017 at 2:03 PM, Neil Henning via llvm-dev
<llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
For SPIR 1.2 you can use this repo + the instructions in it
https://github.com/KhronosGroup/SPIR

I don't believe there is a way to generate SPIR from LLVM trunk.

Cheers,
-Neil.

On 2017-12-02 00:23, Nicholas Wilson via llvm-dev wrote:

I am already successfully generating SPIR-V with a forward port of
Khronos’ SPIR-V LLVM. What does one need in order to generate SPIR?

From what I gather it is _based on_ a specific LLVM IR version (3.4?)
with a bunch of metadata.
Is it possible to generate SPIR from LLVM trunk? If so how?

Thanks
Nic
_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev


_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171220/48a5fdde/attachment.html>