Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify memory model atomic operation language #2449

Open
ewerness-nv opened this issue Oct 22, 2024 · 1 comment
Open

Clarify memory model atomic operation language #2449

ewerness-nv opened this issue Oct 22, 2024 · 1 comment
Assignees

Comments

@ewerness-nv
Copy link

The spec has this language in https://registry.khronos.org/vulkan/specs/1.3-extensions/html/vkspec.html#memory-model-atomic-operation:

Two atomic operations A and B are mutually-ordered if and only if they are potentially-mutually-ordered and any of the following are true:

  • A and B are both device operations.
  • A and B are both host operations.
  • A is a device operation, B is a host operation, and the implementation supports concurrent host- and device-atomics.

There's no bit to indicate that a Vulkan implementation supports concurrent atomics in the last bullet, but it seems weird for the spec to imply a support bit that doesn't exist and assume that we should read it as disable because the bit doesn't exist.

@oddhack
Copy link
Contributor

oddhack commented Oct 23, 2024

Telecon: @jeffbolznv or someone else from the MM TSG will propose MR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants