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

vk: workaround swiftshader spirv no-op issue #7417

Merged
merged 1 commit into from
Dec 8, 2023

Conversation

poweifeng
Copy link
Contributor

Swiftshader runs spirv validation before compilation. However, the validation does not like having Nop (no-op) in the input. So we skip instructions instead of writing no-op for the output of workaroundSpecConstant.

Also, fix issue to keep the value in the original shader if a specialization wasn't provided.

Swiftshader runs spirv validation before compilation. However,
the validation does not like having Nop (no-op) in the input.
So we skip instructions instead of writing no-op for the
output of `workaroundSpecConstant`.

Also, fix issue to keep the value in the original shader if a
specialization wasn't provided.
@poweifeng poweifeng added the internal Issue/PR does not affect clients label Dec 8, 2023
@poweifeng poweifeng merged commit 6116c2f into main Dec 8, 2023
12 checks passed
@poweifeng poweifeng deleted the pf/workaround-spirv-validator branch December 8, 2023 18:32
poweifeng added a commit that referenced this pull request Dec 8, 2023
Swiftshader runs spirv validation before compilation. However,
the validation does not like having Nop (no-op) in the input.
So we skip instructions instead of writing no-op for the
output of `workaroundSpecConstant`.

Also, fix issue to keep the value in the original shader if a
specialization wasn't provided.
poweifeng added a commit that referenced this pull request Dec 8, 2023
Swiftshader runs spirv validation before compilation. However,
the validation does not like having Nop (no-op) in the input.
So we skip instructions instead of writing no-op for the
output of `workaroundSpecConstant`.

Also, fix issue to keep the value in the original shader if a
specialization wasn't provided.
plepers pushed a commit to plepers/filament that referenced this pull request Dec 9, 2023
Swiftshader runs spirv validation before compilation. However,
the validation does not like having Nop (no-op) in the input.
So we skip instructions instead of writing no-op for the
output of `workaroundSpecConstant`.

Also, fix issue to keep the value in the original shader if a
specialization wasn't provided.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Issue/PR does not affect clients
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants