Skip to content

[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

Merged

Conversation

AlexeySachkov
Copy link
Contributor

Related PR: #7313

@AlexeySachkov AlexeySachkov requested a review from a team November 9, 2022 14:28
@AlexeySachkov AlexeySachkov requested a review from a team as a code owner November 9, 2022 14:28
@pvchupin
Copy link
Contributor

pvchupin commented Nov 9, 2022

@AlexeySachkov, is the fail related? Are you working on that?

@AlexeySachkov
Copy link
Contributor Author

@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.

@steffenlarsen
Copy link
Contributor

Failure in set-arg-local-accessor is caused by a conflict with another recent change. intel/llvm-test-suite#1375 should fix it.

@AlexeySachkov AlexeySachkov marked this pull request as draft November 10, 2022 09:15
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.
AlexeySachkov added a commit to AlexeySachkov/llvm that referenced this pull request Nov 10, 2022
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
@AlexeySachkov AlexeySachkov marked this pull request as ready for review November 10, 2022 11:34
@AlexeySachkov
Copy link
Contributor Author

Failed device_num test is not related and will be fixed by #7336

@AlexeySachkov AlexeySachkov merged commit 4be64e7 into intel:sycl Nov 10, 2022
@AlexeySachkov
Copy link
Contributor Author

Fix for post-commit -Werror issue is here: #7357

AlexeySachkov added a commit that referenced this pull request Nov 15, 2022
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
@AlexeySachkov AlexeySachkov deleted the private/asachkov/set-arg-unittest branch May 22, 2024 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants