KhronosGroup / KhronosGroup/OpenCL-CTS

Compiler compiler_defines_for_extensions extension list

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

Description

https://github.com/KhronosGroup/OpenCL-CTS/blob/b79a8a2f42c1c71db3053dedadea43e0ac4fd118/test_conformance/compiler/test_compiler_defines_for_extensions.cpp#L26

The Compiler compiler_defines_for_extensions test having a static list of extension names that needs to be manually updated every time a new extension is released is cumbersome, and causes test failures when the list isn't kept up-to-date.

Can this test be written in a way so that we don't need to maintain an extension list?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with test_conformance/compiler/test_compiler_defines_for_extensions.cpp at the linked test and inspect how its static extension-name list is used. Determine how the test can avoid manually maintaining that list while preserving its validation purpose. Done means the test no longer requires updates whenever a new extension is released and still detects incorrect compiler-defined extensions.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
compilers, testing-qa
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.