arsenm wrote: > So may be we can make the check more permissive for now?
Yes, option 1 is use regex on the return attribute. Option 2 is REQUIRES nvptx registered target. Option 3 is some other way of making sure NVVMIntrRange doesn't run. Something is broken now because it is running at -O0 but it should not be. Option 4 is remove NVVMIntrRange and move the conservative maximum ranges to the intrinsic declarations like this patch did https://github.com/llvm/llvm-project/pull/136196 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
