-
Notifications
You must be signed in to change notification settings - Fork 745
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CUDA] printfs results in ptxas error: Call has wrong number of parameters #1154
Comments
Thats an (undocumented?) intel extension, currently we are only implementing conformant SYCL features. We may do this later on if we have time. |
@bader There is no extension document for this feature? |
@AlexeySachkov, could add documentation for the feature you added by #835 to https://github.com/intel/llvm/tree/sycl/sycl/doc/extensions, please? |
Is this still a problem @fwyzard ? |
@Ruyk It's a problem for me today with the latest version. |
@Ruyk And me today with sycl-nightly/20210330. (@jeffhammond I swear, I'm not trolling your posts. Rather, seem to be some months behind you.) |
Use `::printf` when not compiling for `__SPIR__`, this allows the use of `EmitNVPTXDevicePrintfCallExpr` which packs the var args and dispatches to CUDA's `vprintf`. Fixes intel#1154
Use `::printf` when not compiling for `__SPIR__`, this allows the use of `EmitNVPTXDevicePrintfCallExpr` which packs the var args and dispatches to CUDA's `vprintf`. Fixes #1154
Testing the latest iteration of #1091 (as of 44af06f2eb0) on top of the HEAD of the
sycl
branch (as of 7743e86) with a SYCLE kernel that callsprintf
, the compilation for the CUDA backend fails withAll errors point to similar PTX code:
where
_Z18__spirv_ocl_printfPU3AS4Kcz
demangles to__spirv_ocl_printf(char const AS4*, ...)
.The same kernel compiles and runs with the OpenCL backend.
In case it's useful, the way I am using
printf
in kernel code is here and e.g. here.The code compiles for the CUDA backend if I comment out the call to
cl::sycl::intel::experimental::printf
.The text was updated successfully, but these errors were encountered: