KhronosGroup / KhronosGroup/OpenCL-Docs

access qualifier and kernel launch

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

Description

In OpenCL 2.0, it seems reasonable to want to pass, say, a write_only image or pipe from a parent kernel to be used as a read_only pipe or image in a child kernel. However, the spec gives no indication that an access qualifier changing cast is permitted, and so one may assume that such scenarios are illegal.

But should it be illegal (if it is)? It seems useful to me.

Contributor guide

Open the contributing guide

Research direction

Begin with the OpenCL 2.0 access-qualifier and kernel-launch rules referenced in the issue. Done means reaching a specification decision and documenting whether changing access qualifiers for image or pipe arguments passed to child kernels is permitted.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.