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

Do not selectively apply spirv exts unconditionally do so in spirv_generator #1383

Merged
merged 1 commit into from
Mar 15, 2024

Conversation

diptorupd
Copy link
Contributor

  • Have you provided a meaningful PR description?

Some of the experimental SPIR-V overloads such as the AtomicRef overloads try to set needed SPIR-V extensions flags only for a module that uses such an overload. However, the functionality is broken (see #1262) and needs deeper design changes than are warranted.

We are unconditionally adding needed SPIR-V extension flags in the spirv_generator module. The solution is adequate for now and perhaps should be THE long-term solution.

This PR removes the essentially dead code of adding extra SPIR-V extension flags inside AtomicRef overloads.

@diptorupd diptorupd requested a review from ZzEeKkAa March 14, 2024 07:23
@diptorupd diptorupd force-pushed the unconditionally_apply_spv_exts branch from 99f6015 to 91f9894 Compare March 15, 2024 02:29
@diptorupd diptorupd enabled auto-merge March 15, 2024 02:29
@diptorupd diptorupd merged commit af24e66 into main Mar 15, 2024
56 of 63 checks passed
@diptorupd diptorupd deleted the unconditionally_apply_spv_exts branch March 15, 2024 03:00
github-actions bot added a commit that referenced this pull request Mar 15, 2024
Do not selectively apply spirv exts unconditionally do so in spirv_generator af24e66
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants