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

No explicit coverage of using multiple kernels created from the same source program with different builds #2164

Open
kpet opened this issue Nov 26, 2024 · 0 comments
Labels
missing-coverage mobica-triage Issue proposed for addition to Mobica's backlog (needs WG approval)

Comments

@kpet
Copy link
Contributor

kpet commented Nov 26, 2024

OpenCL programs can be built multiple times, with different options that can affect the behaviour of the kernels. We do not, AFAICT, test this explicitly in the CTS.

Suggested test:

  • Create two buffers
  • Create a program from source (the source contains a single kernel that writes a value defined by a preprocessor macro into a buffer)
  • Build the program, setting the macro to one value
  • Create a kernel from the program
  • Enqueue the kernel, with buffer 1 as a parameter
  • Build the program again, setting the macro to a different value
  • Create a kernel from the program
  • Enqueue the kernel, with buffer 2 as a parameter
  • Call clFinish on the queue
  • Check that both buffers contain different values and the right value for each kernel

Also consider adding a variant using clCompileProgram/clLinkProgram.

@kpet kpet added missing-coverage mobica-triage Issue proposed for addition to Mobica's backlog (needs WG approval) labels Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
missing-coverage mobica-triage Issue proposed for addition to Mobica's backlog (needs WG approval)
Projects
None yet
Development

No branches or pull requests

1 participant