Skip to content

Conversation

bashbaug
Copy link
Contributor

This is a PR to partially address the way we document error conditions, see #1320 and in particular #1320 (comment).

It contains a subset of the changes from #1399, specifically for platforms and devices.

** if _platform_ is not a valid platform
* {CL_INVALID_VALUE}
** if _d3d_device_source_ is not a valid value
** if _d3d_object_ is not valid
Copy link
Contributor

Choose a reason for hiding this comment

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

is this error code new? Can't see anything about _d3d_object_ in the previous CL_INVALID_VALUE wording

same question for the clGetDeviceIDsFromD3D11KHR changes

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think I added this for parity with clGetDeviceIDsFromDX9MediaAdapterKHR, specifically:

CL_INVALID_VALUE if any of the entries in media_adapters_type or media_adapters is not a valid value.

But, you're right, strictly speaking this wasn't an error condition previously. I've commented it out for now, and we can have the discussion later.

@bashbaug
Copy link
Contributor Author

Merging as discussed in the August 26th teleconference.

@bashbaug bashbaug merged commit 4db6186 into KhronosGroup:main Aug 26, 2025
2 checks passed
@bashbaug bashbaug deleted the error-code-consistency-part-one branch August 26, 2025 18:36
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.

2 participants