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
In the rng mklcpu backend in philox4x32x10.cpp the same kernel names are generated for both the USM and buffer API. This does not cause an error when using dpc++, but according to the SYCL standard, this is illegal and causes problems with some SYCL implementations, tested with hipSYCL.
Observed behavior
For example, the kernels at line 328 and 68 in philox4x32x10.cpp appear to have the same name. This is a result of the combination of the type of distr and philox4x32x10_impl being used as kernel names. Since kernels are declared for both USM and buffer interfaces with the same type of distr this results in ambiguous kernel names.
Expected behavior
All kernels should have a unique name.
The text was updated successfully, but these errors were encountered:
sbalint98
changed the title
Rng mklcpu backend violates uses ambiguous kernel names
Rng mklcpu backend uses ambiguous kernel names
May 10, 2021
Summary
In the rng mklcpu backend in
philox4x32x10.cpp
the same kernel names are generated for both the USM and buffer API. This does not cause an error when using dpc++, but according to the SYCL standard, this is illegal and causes problems with some SYCL implementations, tested with hipSYCL.Observed behavior
For example, the kernels at line 328 and 68 in
philox4x32x10.cpp
appear to have the same name. This is a result of the combination of the type ofdistr
andphilox4x32x10_impl
being used as kernel names. Since kernels are declared for both USM and buffer interfaces with the same type ofdistr
this results in ambiguous kernel names.Expected behavior
All kernels should have a unique name.
The text was updated successfully, but these errors were encountered: