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

Update clUpdateMutableCommandsKHR binding #298

Merged
merged 1 commit into from
Sep 6, 2024

Conversation

EwanC
Copy link
Contributor

@EwanC EwanC commented Jul 31, 2024

In OpenCL-Docs PR KhronosGroup/OpenCL-Docs#1045 the API for cl_khr_command_buffer_mutable_dispatch API clUpdateMutableCommandsKHR changed in a breaking way.

When the headers update OpenCL-Headers PR KhronosGroup/OpenCL-Headers#245 the bindings will break if they are not updated to reflect this change.

Bindings updated in this PR to pass to arrays of templated length to the C++ method. The underlying .data() pointers of these parameters can be passed through to the OpenCL API. I don't think any tests for this API currently exist in the repo to be updated.

@CLAassistant
Copy link

CLAassistant commented Jul 31, 2024

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

@bashbaug bashbaug left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes look good, but they'll break without the corrosponding header updates. Should we use the extension versioning mechanism to either a) only expose this function when the headers are sufficiently new, or b) select between both versions, for some time at least?

In OpenCL-Docs PR KhronosGroup/OpenCL-Docs#1045
the API for `cl_khr_command_buffer_mutable_dispatch` API
`clUpdateMutableCommandsKHR` changed in a breaking way.

When the headers update OpenCL-Headers PR KhronosGroup/OpenCL-Headers#245
the bindings will break if they are not updated to reflect this
change.

Bindings updated in this PR to pass to arrays of templated length to
the C++ method. The underlying `.data()` pointers of these parameters can be
passed through to the OpenCL API.
@EwanC
Copy link
Contributor Author

EwanC commented Sep 4, 2024

These changes look good, but they'll break without the corrosponding header updates. Should we use the extension versioning mechanism to either a) only expose this function when the headers are sufficiently new, or b) select between both versions, for some time at least?

I forgot to reply when I made this change, but I updated to option b)

Copy link
Contributor

@bashbaug bashbaug left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merging as discussed in the September 3rd teleconference + email.

@bashbaug bashbaug merged commit c58621d into KhronosGroup:main Sep 6, 2024
49 of 54 checks passed
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