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
Many applications written in CUDA rely on the whole device synchronization behavior of cudaDeviceSynchronize().
Trying to migrate applications that use this to SYCL, for example, is not really possible.
Question: Why does this need to be in L0? Why can't you solve it at a higher level?
Answer: The higher level layer may not have 100% visibility over how level zero is being used. If the L0 plugin in DPC++ tried to add something like this - programs may have incorrect behavior if the user application ALSO uses L0 directly - the plugin has no knowledge of any queues created in the user application or libaries.
The text was updated successfully, but these errors were encountered:
Many applications written in CUDA rely on the whole device synchronization behavior of cudaDeviceSynchronize().
Trying to migrate applications that use this to SYCL, for example, is not really possible.
Question: Why does this need to be in L0? Why can't you solve it at a higher level?
Answer: The higher level layer may not have 100% visibility over how level zero is being used. If the L0 plugin in DPC++ tried to add something like this - programs may have incorrect behavior if the user application ALSO uses L0 directly - the plugin has no knowledge of any queues created in the user application or libaries.
The text was updated successfully, but these errors were encountered: