You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CUDA and HIP provide the CUDA_LAUNCH_BLOCKING and HIP_LAUNCH_BLOCKING environment variables, which force synchronous kernel launches and make it easier to obtain a backtrace for a failing kernel. Since SYCL does not appear to offer a similar mechanism, would it be possible to introduce something like OCCA_LAUNCH_BLOCKING that forces a device–host synchronization after each kernel launch? This would at least help users identify the first failing kernel more quickly.
Something like manually calling device.finish() for each kernel launches?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
CUDA and HIP provide the
CUDA_LAUNCH_BLOCKINGandHIP_LAUNCH_BLOCKINGenvironment variables, which force synchronous kernel launches and make it easier to obtain a backtrace for a failing kernel. Since SYCL does not appear to offer a similar mechanism, would it be possible to introduce something likeOCCA_LAUNCH_BLOCKINGthat forces a device–host synchronization after each kernel launch? This would at least help users identify the first failing kernel more quickly.Something like manually calling
device.finish()for each kernel launches?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions