Closed al42and closed 4 months ago
@al42and thank you for reporting! we will look into it in few days. Any chances to check it with recent oneAPI release?
@jfedorov: I was using open-source IntelLLVM above. But the problem can be reproduced with oneAPI 2024.0 (Intel(R) oneAPI DPC++/C++ Compiler 2024.0.0 (2024.0.0.20231017)).
Note: when compiling with icpx
, one would have to change line 8 to using gsl = syclex::info::graph_support_level;
, because the SYCL Graph API is unstable.
@al42and Thank you. will look into it.
@al42and This issue is indeed reproduced (~three weeks ago) and hopefully will be fixed soon. thank you.
As of ze_tracer 1b7929b8139b09b03127c92211a9be2be9fb900e, the issue still reproduces with ICPX 2024.1.2, but not with the open-source IntelLLVM 2838f40382bedddbda0a5f20ebeeba86310044da. So, looks like some nasty behavior in the IntelLLVM/UR?
Works fine with ICPX 2024.2.0 and latest open-source IntelLLVM build. :+1:
Trying to trace a simple application which uses SYCL Graphs with ze_tracer or onetrace triggers an internal failed assertion.
Ubuntu Linux 22.04 (6.2.0-36-generic), Intel Compute Runtime 23.30.26918.9, recent Intel LLVM built from source (a2f02214200ef71d3a8ec6cae1b84a16508513c4), PTI-GPU 90b9230c8bd9c00211934ec5e36183edc3aa8c1d.
Source code:
Stack trace:
Output with
SYCL_PI_TRACE=-1
: sycl_pi_trace.log