Skip to content
This repository has been archived by the owner on Jun 28, 2022. It is now read-only.

clGetKernelArgInfo functions #46

Open
trbauer opened this issue Mar 3, 2016 · 2 comments
Open

clGetKernelArgInfo functions #46

trbauer opened this issue Mar 3, 2016 · 2 comments

Comments

@trbauer
Copy link

trbauer commented Mar 3, 2016

These are OpenCL 1.2. This would entail adding:

clGetKernelArgTypeName :: CLKernel -> Int -> IO String
clGetKernelArgName :: CLKernel -> Int -> IO String
clGetKernelArgAddressQualifier :: CLKernel -> Int -> IO CLKernelArgAddressQualifier
clGetKernelArgAccessQualifier :: CLKernel -> Int -> IO CLKernelArgAccessQualifier
clGetKernelArgTypeQualifier :: CLKernel -> Int -> IO CLKernelArgTypeQualifier
And the enumerations for the latter 3.
data CLKernelArgAddressQualifier =
CL_KERNEL_ARG_ADDRESS_GLOBAL
| ...
... etc

I wouldn't mind implementing this and setting up a pull request (this would be my first).

@zhensydow
Copy link
Contributor

Hi, I thinked about it some time ago, and maybe the best way its to make a branch for OpenCL 1.2 instead of merge it on the main branch.

So, we can always generate 1.0.X packages for the people doesn't have 1.2 drivers.

Thanks

@trbauer
Copy link
Author

trbauer commented Mar 4, 2016

Why not retain one branch only, but can we include a preprocessor flag (cabal) option to include or omit 1.2 stuff. This would make validation and maintenance more uniform (don't have to keep two branches in sync). In addition, I don't want all of 1.2, just a few functions at the moment. A 1.2 branch or sort of implies that we support and validate everything right?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants