Skip to content

Conversation

@s-perron
Copy link
Collaborator

The current implementation of OpExecutionModeId assumes that the
operands must be OpConstants. However, they could be the id of a
spec constant. The first step in allowing OpExecutionModeId is to modify
the internal representation of the instruction to hold general spirv
instructions.

Part of #5960
and #3092.

@s-perron
Copy link
Collaborator Author

FYI: @danbrown-amd

Copy link
Collaborator

@Keenuts Keenuts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some bits, but overall LGTM

The current implementation of OpExecutionModeId assumes that the
operands must be OpConstants. However, they could be the id of a
spec constant. The first step in allowing OpExecutionModeId is to modify
the internal representation of the instruction to hold general spirv
instructions.

Part of microsoft#5960
and microsoft#3092.
@s-perron s-perron enabled auto-merge (squash) April 29, 2025 13:30
@s-perron s-perron merged commit e866b4b into microsoft:main Apr 29, 2025
12 checks passed
@github-project-automation github-project-automation bot moved this from New to Done in HLSL Roadmap Apr 29, 2025
@s-perron s-perron deleted the exe_mode_id branch April 29, 2025 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants