KhronosGroup / KhronosGroup/OpenCL-Docs

Discrepancy between specification and XML/headers around CL-GL interop function prototypes

Open
#732 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
421
Forks
132
Avg merge
5d 13h
Merged PRs (30d)
11

Description

The extension specification uses GLenum, GLint and GLuint but the headers and XML use and define cl_GLenum, cl_GLint and cl_GLuint. I'm guessing this was done to avoid a dependency on the OpenGL headers. Maybe we could conditionally define aliases to the GL types when those are not already defined? I assume that sizes, etc are all correct so this is mostly cosmetic but might still confuse people.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare the extension specification's CL-GL prototypes with the corresponding headers and XML definitions, starting from the definitions of cl_GLenum, cl_GLint, and cl_GLuint. Review how these relate to GLenum, GLint, and GLuint and the stated goal of avoiding OpenGL header dependencies. Done means the specification, headers, and XML consistently describe the agreed types.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, xml
Domain
api, documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.