KhronosGroup / KhronosGroup/OpenCL-Docs

interactions between clSetKernelArg and cl_ext_immutable_memory_objects need to be specified.

Open
#1,438 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
420
Forks
131
Avg merge
5d 13h
Merged PRs (30d)
11

Description

The OpenCL CTS already tests for this, but I think the spec also needs to be adjusted there:

CL_INVALID_ARG_VALUE
- if the argument is a buffer and arg_value refers to an image object created with cl_mem_flags of CL_MEM_IMMUTABLE_EXT, or
- if the argument is an image declared with the read_only qualifier and arg_value refers to an image object created with cl_mem_flags of CL_MEM_WRITE_ONLY, or
- if the image argument is declared with the write_only qualifier and arg_value refers to an image object created with cl_mem_flags of CL_MEM_READ_ONLY or CL_MEM_IMMUTABLE_EXT.

Anything I'm missing there (should probably have created a PR directly...)?

Contributor guide

Open the contributing guide

Research direction

Start by locating the specification text for clSetKernelArg and the cl_ext_immutable_memory_objects extension, then compare the stated cases with the existing OpenCL CTS coverage. Check whether any interaction cases are missing. Done means the specification defines the relevant CL_INVALID_ARG_VALUE behavior and remains consistent with the CTS tests.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.