Incorrect sycl::buffer
initialization in the struct __usm_or_buffer_accessor
constructor
#1914
Labels
sycl::buffer
initialization in the struct __usm_or_buffer_accessor
constructor
#1914
Incorrect
sycl::buffer
initialization in thestruct __usm_or_buffer_accessor
constructor:This isn't a new bug from this PR, but I think that
__no_init
it is wrong to be using at all times here I think this is something that we need to specify each time and only when it is proper.While this is temporary memory, it is often used to bridge between multiple kernels where the second kernel reads before it writes (if it does write). In this case I believe
__no_init
is wrong.The text was updated successfully, but these errors were encountered: