[SYCl][L0] Buffer for multi-device context is using device allocation now #976
Conversation
|
/verify with intel/llvm#5966 |
|
/verify with intel/llvm#5966 |
… now Signed-off-by: Sergey V Maslov <sergey.v.maslov@intel.com>
Signed-off-by: Sergey V Maslov <sergey.v.maslov@intel.com>
Signed-off-by: Sergey V Maslov <sergey.v.maslov@intel.com>
Signed-off-by: Sergey V Maslov <sergey.v.maslov@intel.com>
| char *Ptr = (char *)HostBuffer1; | ||
| for (int i = 0; i < 10; i++) { | ||
| assert(Ptr[i] == 'a'); | ||
| } |
There was a problem hiding this comment.
@againull : from the spec you crafted:
A SYCL buffer that is constructed with this interop API uses the Level Zero memory allocation for its full lifetime, and the contents of the Level Zero memory allocation are unspecified for the lifetime of the SYCL buffer. If the application modifies the contents of that Level Zero memory allocation during the lifetime of the SYCL buffer, the behavior is undefined.
|
/verify with intel/llvm#5966 |
1 similar comment
|
/verify with intel/llvm#5966 |
Signed-off-by: Sergey V Maslov <sergey.v.maslov@intel.com>
|
/verify with intel/llvm#5966 |
I cannot reproduce this locally. @againull , @cperkinsintel any idea? |
|
Basic/context-with-multiple-devices.cpp is a known failure we are trying to track down. I have a PR to disable it ( #983 ) however, I strongly suspect that if we disable it, the failure will simply show up somewhere else. Seems to be some sort of infrastructure problem. Not sure. |
3 participants
Signed-off-by: Sergey V Maslov sergey.v.maslov@intel.com