KhronosGroup / KhronosGroup/Vulkan-Docs

VK_AMDX_shader_queue: Confusion between shader index and node index

Open
#2,226 1 comment 0 reactions 1 assignee View on GitHub

@Tobski is already working on this.

Since Sep 20, 2023.

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

Description

I'm confused about what the difference between shader index is really meant to be. The proposals tries to clarify by saying the following:

To summarize, execution graphs use two kinds of indexes:

  • shader index specified in VkPipelineShaderStageNodeCreateInfoAMDX and used to enqueue payloads
  • node index specified in VkDispatchGraphInfoAMDX and used only for launching the graph from a command buffer.

Yet the final operand of OpInitializeNodePayloadsAMDX is called Node Index. Is this just a typo ?

@Tobski

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.