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

inconsistent error codes in Appendix F #1095

Closed
bashbaug opened this issue Mar 25, 2024 · 1 comment · Fixed by #1119
Closed

inconsistent error codes in Appendix F #1095

bashbaug opened this issue Mar 25, 2024 · 1 comment · Fixed by #1119
Assignees
Labels
OpenCL API Spec Issues related to the OpenCL API specification.

Comments

@bashbaug
Copy link
Contributor

After #950, the error code appendix table has an error code for cl_khr_icd, but no error codes for other extensions. Do we want to include error codes for extensions in this table, or should it only contain error codes for the core spec?

The primary reason for the error code appendix was to have a place for the error codes to link to (although the text description for each of the error codes is also a nice benefit). If there is already some other place the extension error codes can link to we can use that instead, although currently many enum error codes do not seem to link to anything.

@bashbaug bashbaug added the OpenCL API Spec Issues related to the OpenCL API specification. label Mar 25, 2024
@bashbaug
Copy link
Contributor Author

Discussed in the March 26th teleconference. Preference is to include error codes for extensions in the same table.

Ideally we would generate the error codes from the XML file, but that can come later.

@bashbaug bashbaug changed the title inconsistent error codes in Appendix I inconsistent error codes in Appendix F Mar 31, 2024
@bashbaug bashbaug self-assigned this Mar 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OpenCL API Spec Issues related to the OpenCL API specification.
Development

Successfully merging a pull request may close this issue.

1 participant