-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL][ESIMD] Fix an error when a scalar offset is provided as a parameter to the API #8075
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
# Conflicts: # sycl/include/sycl/ext/intel/esimd/memory.hpp
Complementary test PR: intel/llvm-test-suite#1534 |
/verify with intel/llvm-test-suite#1534 |
Emulator failure at dword_atomic_smoke.cpp is fixed in the test PR |
/verify with intel/llvm-test-suite#1534 |
Looks good to me. The only question that stops me from approving it is this one: If I understand it correctly, this PR is motivated by some regression, |
The test that failed is a benchmark test that seems not to run regularly and that is why the issue wasn't discovered earlier. |
Temporarily cancel my approval. I want to ensure that multiple/vector stores to same offset and atomic vector updates are safe from GPU/hardware point of view and is not undefined behavior
# Conflicts: # sycl/include/sycl/ext/intel/esimd/memory.hpp
…calarOffset # Conflicts: # sycl/include/sycl/ext/intel/esimd/memory.hpp
Test failure OptionalKernelFeatures/is_compatible.cpp is not related to the change |
No description provided.