-
Notifications
You must be signed in to change notification settings - Fork 75
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
get_supported_image_formats fails on Mac OS X #67
Comments
Ok looks like there are some Apple-specific image channel orders that I need to include in the definition for ImageChannelOrder. I'll look through the relevant extension header file and add them :) |
I failed to read the last line of your post. I'm in the same boat. Those image channel orderings are unspecified. This will be a wontfix until we can find some sort of definition for those values. Thanks for your investigative work. |
Or maybe in |
I was thinking about creating an additional enum variant, something like I'm eager to be convinced. Until then I think it's only correct that it remains an error. |
Yeah I also cannot think of any reasons why one might want to know about an unspecified image format. But I would prefer |
Ok, I'll add an |
cogciprocate/ocl-core@6ce4f27 and 5c0fde4 should take care of it. Image formats returned from info functions are now individually wrapped in a |
Works great, thank you very much for your work!
|
Excellent :) |
core::get_supported_image_formats
fails on OSX by returningThe reason is that some of the returned values for channel order and datatype are completely weird. On the CPU device I get:
On the GPU device:
The values were determined using this small C program (posting it here because maybe I made a mistake somewhere?)
Doing the same thing using
cl-sys
yields the same results.I could not find any of those strange values in Apple's OpenCL headers.
The text was updated successfully, but these errors were encountered: