c11_atomics `{svm_,}atomic_fence` test issues

Open
#2,544 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
testing-qa

Research direction

Locate the c11_atomics tests for atomic_fence and svm_atomic_fence, then read the related coverage and the discussion linked from issue #2496. Confirm which assumptions are not guaranteed and disable the affected tests as agreed; done means the tests no longer run while the issue remains tracked.

Written by the indexing model from the issue text.

Description

Several implementers have reported issues over the years with the atomic_fence and svm_atomic_fence tests, the latest being #2496.

Analysis from a few years ago (e.g. https://www.khronos.org/members/login/bugzilla/show_bug.cgi?id=15814) suggests that the tests are incorrect and make assumptions that are not guaranteed to hold. This was discussed in the 2025/10/14 teleconference and we agreed to disable the tests and create this issue for tracking.

Dominant language
C++
Stars
234
Forks
240
Avg merge
6d 12h
Merged PRs (30d)
15

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from KhronosGroup/OpenCL-CTS

All issues in KhronosGroup/OpenCL-CTS

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.