KhronosGroup / KhronosGroup/OpenCL-CTS

Scope of the CTS - Compile Time versus Run Time tests

Open
#1,161 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
232
Forks
235
Avg merge
8d 7h
Merged PRs (30d)
18

Description

Just creating this issue as a discussion point from over at the OpenCL CTS Framework. Currently, the CTS tests run-time characteristics of OpenCL implementations. Does it make sense to extend this to compile-time tests as well, such that offline OpenCL C compilers can be validated too? Bringing this in from the OpenCL CTS Framework documentation here:

https://github.com/KhronosGroup/OpenCL-CTS-Framework/tree/master/03-conformance-checks

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked OpenCL CTS Framework documentation, especially the conformance-checks section, and compare its runtime testing scope with the proposed compile-time coverage. Define what offline OpenCL C compiler validation would include and how completion would be evaluated; the issue currently provides no files or tests to change.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
compilers, testing-qa
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.