[clang] [llvm] [NVPTX] Revamp NVVMIntrRange pass (PR #94422)
Jay Foad via cfe-commits
cfe-commits at lists.llvm.org
Thu Jun 6 07:55:29 PDT 2024
================
@@ -6,21 +6,21 @@
__attribute__((global))
void kernel(int *out) {
int i = 0;
- out[i++] = threadIdx.x; // CHECK: call noundef i32 @llvm.nvvm.read.ptx.sreg.tid.x()
- out[i++] = threadIdx.y; // CHECK: call noundef i32 @llvm.nvvm.read.ptx.sreg.tid.y()
- out[i++] = threadIdx.z; // CHECK: call noundef i32 @llvm.nvvm.read.ptx.sreg.tid.z()
+ out[i++] = threadIdx.x; // CHECK: call noundef {{.*}} i32 @llvm.nvvm.read.ptx.sreg.tid.x()
----------------
jayfoad wrote:
@AlexMaclean I also see this problem on some internal test machines. It seems suspicious - is there some nondeterminism? Or is there a good reason why some machines would not add the range metadata here???
https://github.com/llvm/llvm-project/pull/94422
More information about the cfe-commits
mailing list