-
Notifications
You must be signed in to change notification settings - Fork 130
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
revisit handling for extensions #146
Comments
alycm
added a commit
to alycm/OpenCL-CLHPP
that referenced
this issue
Sep 6, 2021
Newly tested defines: * `CL_HPP_USE_CL_DEVICE_FISSION` (corrected from `CL_HPP_ENABLE_DEVICE_FISSION`) * `CL_HPP_USE_CL_IMAGE2D_FROM_BUFFER_KHR` The `CL_HPP_NO_STD_FOO` defines are not tested, because the header won't build unless an alternative implementation is provided. `The CL_HPP_USE_DX_INTEROP` define is not tested because it does not work on platforms without DirectX headers. Issue KhronosGroup#146 could make this irrelevant, but easy to test these defines in the meantime.
bashbaug
pushed a commit
that referenced
this issue
Sep 15, 2021
Newly tested defines: * `CL_HPP_USE_CL_DEVICE_FISSION` (corrected from `CL_HPP_ENABLE_DEVICE_FISSION`) * `CL_HPP_USE_CL_IMAGE2D_FROM_BUFFER_KHR` The `CL_HPP_NO_STD_FOO` defines are not tested, because the header won't build unless an alternative implementation is provided. `The CL_HPP_USE_DX_INTEROP` define is not tested because it does not work on platforms without DirectX headers. Issue #146 could make this irrelevant, but easy to test these defines in the meantime.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Creating this issue in response to a review comment: #140 (review)
We currently have a handful of defines in the C++ bindings for extensions. Are these needed? If not, we can remove the defines to simplify testing (this is preferred)? If so, do we need to add defines for other extensions?
The text was updated successfully, but these errors were encountered: