KhronosGroup / KhronosGroup/SPIRV-Registry

Is it valid to have duplicate Execution Modes

Open
#150 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
149
Forks
99
Avg merge
4d 21h
Merged PRs (30d)
2

Description

Came across this while writing validation for https://github.com/KhronosGroup/SPIRV-Tools/pull/4828

I assume the following is not actually allowed, but `spirv-val` doesn't check it and nothing in spec to refer to it being illegal.
```swift
OpExecutionMode %entrypoint LocalSize 1 2 1
OpExecutionMode %entrypoint LocalSize 1 1 2
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the duplicate OpExecutionMode examples in this issue and the referenced SPIRV-Tools pull request #4828. Check the SPIR-V specification for rules governing repeated execution modes, then clarify whether the example is valid and update the relevant specification text or validation guidance if needed.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.