Catch a PI CUDA ERROR in try catch block?

[Aympab]

Hello,

I am running the same SYCL code on different GPUs (NVIDIA and AMD). The two backends have different limits in terms of grid size.
When running with a too large size for the y-dimension of the CUDA grid, I get this plugin interface error:

PI CUDA ERROR:
        Value:           1
        Name:            CUDA_ERROR_INVALID_VALUE
        Description:     invalid argument
        Function:        cuda_piEnqueueKernelLaunch
        Source Location: /opt/sycl/source/llvm/sycl/plugins/cuda/pi_cuda.cpp:3186

I would like to manage this PI exception using a try catch block, but sycl::exception and std::exception don't seem to catch it. Any ideas how to manage this exception in a portable way (i.e. that will compile with another SYCL implementation/backend)?

[AlexeySachkov]

Tagging @intel/llvm-reviewers-cuda here to comment. I don't know much about our CUDA plugin implementation, but this looks rather like a bug to mee. SYCL interface for error reporting is exceptions and it shouldn't matter which exact device/backend we are running on.

[JackAKirk]

There is a way that was agreed in UR to allow these native errors to be passed to sycl exceptions:
oneapi-src/unified-runtime#500 (comment)

I believe UR team is in the process of adapting all cases to correctly return a sycl exception whilst maintaining this degree of native error information for the user. @kbenzie may comment further.

At the moment the native error is printed without using the mechanism that results in a sycl::exception as a short term fix to allow users to see meaningful error information. This prioritizes sensible error messages, at the expense that no sycl::exception is passed along the stack.