-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL] Add unittest for recent handler::set_arg fixes #7333
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
[SYCL] Add unittest for recent handler::set_arg fixes #7333
Conversation
@AlexeySachkov, is the fail related? Are you working on that? |
The fail is absolutely related, because the newly added test is failing in CI. I will be looking into it, even though I'm not yet able to reproduce it in my local environment. |
Failure in set-arg-local-accessor is caused by a conflict with another recent change. intel/llvm-test-suite#1375 should fix it. |
This reverts commit 723c769.
This is needed to avoid jumps based on unconditional value in program_impl constructor
In unit tests we don't have proper mock implementations for all PI calls, which can lead to some out-parameters not being set which in turn may cause obscure errors.
This patch aims to improve situation with unit-tests: a lot of PI routines only hace dummy mock versions of them. Dummy mocks ignore all arguments, leaving out-parameters untoched. Depending on how they used at call site, this could lead to some obscure errors like `bad_alloc` if an uninitialized value was used to set a size of a `vector`. Discovered while working on a unit-test in intel#7333
Failed |
Fix for post-commit |
This patch aims to improve situation with unit-tests: a lot of PI routines only have dummy mock versions of them. Dummy mocks ignore all arguments, leaving out-parameters untouched. Depending on how they used at call site, this could lead to some obscure errors like `bad_alloc` if an uninitialized value was used to set a size of a `vector`. Discovered while working on a unit-test in #7333
Related PR: #7313