jhuber6 wrote:

> @JonChesterfield even if you distinguish spirv64 from amdgpu in cmake clang 
> doesn't make that distinction. A common pattern for spriv64 is to return null 
> if its not AMDGPU.

General question, what's the expected way to access things like thread IDs and 
such from SPIR-V? The presence of the `spirv64--` and `spirv64-amd-amdhsa` 
confuses me, since I would've assumed that SPIR-V would have some builtins, but 
as far as I can tell the current state of the art is just to emit builtins that 
the underlying target uses, like AMD. At that point, what's the benefit of 
SPIR-V compared to LLVM-IR?

https://github.com/llvm/llvm-project/pull/128585
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to