KhronosGroup / KhronosGroup/OpenCL-Docs

Clarify which half types and builtins need cl_khr_fp16 and which do not.

Open
#1,188 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

Current spec sections of interest

- Spec requires cl_khr_fp16 for functions taking or returning half types as per https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_C.html#vector-data-load-and-store-functions.
- Specification for halfn requires cl_khr_fp16 as per footnote https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_C.html#_footnotedef_8

Also refer to discussion on CTS PR https://github.com/KhronosGroup/OpenCL-CTS/pull/1974

Contributor guide

Open the contributing guide

Research direction

Start by comparing the OpenCL C vector data load/store section with the halfn footnote, then review the discussion on OpenCL-CTS PR 1974. Document which half types and builtins require cl_khr_fp16 and which do not, with the specification wording made consistent.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.