search for: fontend

...library to link the generated code to, to live in an external repo. This is fine because SPIR<->LLVM IR is trivial, SPIR-V<->LLVM is not. Having the SPIR-V <-> LLVM-IR conversion part of the tool as an external repo as opposed to the llvm would make it very difficult to use as a fontend: First the changes to the build pipeline are a hinderance. In my fork of SPIRV-LLVM the backend is a target because I couldn’t get CMake to link the libraries to LDC as a support library. This would be made even more complicated with at external project. I would probably resort to invoking an ext...

Hi, for a few months already I have been asking around for opinions on how people could best work together on Khronos' SPIR-V <-> LLVM-IR converter and some consensus seems to have formed. Most of the people I talked to favored having the converter become an external tool within the LLVM project, similar to libclc. I think that the LLVM project's processes, infrastructure and

...ated code to, to live in an external repo. > > This is fine because SPIR<->LLVM IR is trivial, SPIR-V<->LLVM is not. > > Having the SPIR-V <-> LLVM-IR conversion part of the tool as an external repo as opposed to the llvm would > make it very difficult to use as a fontend: > > First the changes to the build pipeline are a hinderance. In my fork of SPIRV-LLVM the backend is a target > because I couldn’t get CMake to link the libraries to LDC as a support library. This would be made even more > complicated with at external project. I would probably resort...