search for: etnativ

...g and updating.) One user of that external tool will be Mesa [1] (for its OpenCL implementation named clover) for 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by translating SPIR-V to LLVM IR; (patches under review [2]) 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating from SPIR-V to NIR). Regards, Pierre [1]: https://www.mesa3d.org/ [2]: https://patchwork.freedesktop.org/series/38728/ > It's important to demonstrate that there is a developer community...

...e user of that external tool will be Mesa [1] (for its OpenCL implementation > named clover) for > 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by > translating SPIR-V to LLVM IR; (patches under review [2]) > 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by > clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating > from SPIR-V to NIR). > > Regards, > Pierre > > [1]: https://www.mesa3d.org/ > [2]: https://patchwork.freedesktop.org/series/38728/ > >> It's important to...

...e user of that external tool will be Mesa [1] (for its OpenCL implementation > named clover) for > 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by > translating SPIR-V to LLVM IR; (patches under review [2]) > 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by > clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating > from SPIR-V to NIR). > > Regards, > Pierre > > [1]: https://www.mesa3d.org/ > [2]: https://patchwork.freedesktop.org/series/38728/ > >> It's important to de...

...g and updating.) One user of that external tool will be Mesa [1] (for its OpenCL implementation named clover) for 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by translating SPIR-V to LLVM IR; (patches under review [2]) 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating from SPIR-V to NIR). Regards, Pierre [1]: https://www.mesa3d.org/ [2]: https://patchwork.freedesktop.org/series/38728/ > It's important to demonstrate that there is a developer community...

...xternal tool will be Mesa [1] (for its OpenCL implementation >> named clover) for >> 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by >> translating SPIR-V to LLVM IR; (patches under review [2]) >> 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by >> clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating >> from SPIR-V to NIR). >> >> Regards, >> Pierre >> >> [1]: https://www.mesa3d.org/ >> [2]: https://patchwork.freedesktop.org/series/38728/ >...

On 02/21/2018 12:15 AM, Tomeu Vizoso via llvm-dev wrote: > 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

...xternal tool will be Mesa [1] (for its OpenCL implementation >> named clover) for >> 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by >> translating SPIR-V to LLVM IR; (patches under review [2]) >> 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by >> clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating >> from SPIR-V to NIR). >> >> Regards, >> Pierre >> >> [1]: https://www.mesa3d.org/ >> [2]: https://patchwork.freedesktop.org/series/38728/ >&g...

...l be Mesa [1] (for its OpenCL implementation >>> named clover) for >>> 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by >>> translating SPIR-V to LLVM IR; (patches under review [2]) >>> 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by >>> clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating >>> from SPIR-V to NIR). >>> >>> Regards, >>> Pierre >>> >>> [1]: https://www.mesa3d.org/ >>> [2]: https://patchwork.fr...

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