Skip to content
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

Command buffer testing fixes #2081

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

gorazd-sumkovski-arm
Copy link
Contributor

No description provided.

@gorazd-sumkovski-arm gorazd-sumkovski-arm changed the title Command buffer Command buffer testing fixes Sep 12, 2024
One of the checks in the test was using an image for the destination of
`clCommandCopyImageToBufferKHR()` but this needs to be a buffer.

Signed-off-by: Gorazd Sumkovski <gorazd.sumkovski@arm.com>
The allocated `buffer` is used as an output buffer when copying from
`image`, so it needs to be at least as large.

Signed-off-by: Gorazd Sumkovski <gorazd.sumkovski@arm.com>
In the setup of `negative_command_ndrange_kernel_not_support_printf` and
`negative_command_ndrange_kernel_with_enqueue_call`, the program was
being built without having been first created.

Signed-off-by: Gorazd Sumkovski <gorazd.sumkovski@arm.com>
When there are no properties, the value passed as `param_value_size` is
-1, but since the argument is of type `size_t`, this is interpreted as a
really big value (and hence not an invalid value, as the test intends).

Moreover, if the `command_buffer` was created without properties, then
even a size of 0 is large enough to store them. This test requires
`command_buffer` to have properties for there to be invalid values for
`param_value_size`.

Signed-off-by: Gorazd Sumkovski <gorazd.sumkovski@arm.com>
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.

1 participant