KhronosGroup / KhronosGroup/Vulkan-Docs

Is `VK_PIPELINE_STAGE_ALL_*` equivalent to `VK_PIPELINE_STAGE_2_ALL_*`?

Open
#2,235 1 comment 1 reaction 1 assignee View on GitHub

@Tobski is already working on this.

Since Sep 27, 2023.

Dominant language
JavaScript
Stars
3.3k
Forks
549
Avg merge
5d 5h
Merged PRs (30d)
2

Description

Is VK_PIPELINE_STAGE_ALL_* Bit strictly equivalent to VK_PIPELINE_STAGE_2_ALL_*?

By principle of least surprise it feels that shuld be so.

But interpretation of the spec sneking to my mind is that VK_PIPELINE_STAGE_ALL_* includes only stages defined in VkPipelineStageFlagBits(1). Notably, the specification of VK_PIPELINE_STAGE_2_ALL_GRAPHICS_BIT explicitly mentions stages that are lacking in VK_PIPELINE_STAGE_ALL_GRAPHICS_BIT descriptions.

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.