KhronosGroup / KhronosGroup/OpenCL-Docs

No specified maximum length for a kernel name

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

Description

A while ago I requested that we add testing for kernels with long names to the CTS (https://github.com/KhronosGroup/OpenCL-CTS/issues/2422). As part of creating the issue, I was looking for a statement about the maximum length in the specification but could not find any at the time. There doesn't seem to be any limit at all in OpenCL C and it seems we default to universal SPIR-V limits in SPIR-V programs.

Should we have a specified maximum length for kernel names? It seems like it would be useful for applications/middleware that generate long kernel names.

We may want something like a device query with a mandated minimum value or maybe just a mandated minimum value? We probably want the same limit to apply to both OpenCL C and SPIR-V so conversions and round-tripping are possible.

Contributor guide

Open the contributing guide

Research direction

The issue names no source file or test. Start by reviewing the relevant OpenCL C and SPIR-V specification sections and the linked CTS issue; done means the project agrees on a kernel-name limit and documents consistent requirements for both languages, with any needed validation identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
documentation
Issue type
Feature
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.