Skip to content

Conversation

@bashbaug
Copy link
Contributor

Adds initial (preview) support for device scope barriers via SPV_INTEL_device_barrier.

See: intel/llvm#12092

@bashbaug
Copy link
Contributor Author

Marking as a draft to coordinate merge order.

@bashbaug bashbaug marked this pull request as draft November 21, 2025 15:07
By removing the error diagnostic, the SPIR-V LLVM translator behaves
the same as it did previously as long as the device barrier extension
is disabled.
@bashbaug
Copy link
Contributor Author

bashbaug commented Dec 1, 2025

@MrSidims I've made the changes we discussed (and resolved the related converations), please take a look.

Specficially:

  1. I removed the error diagnostic for use of the device execution scope when the extension is disabled, for now. I'm still not super happy about this, but I do agree this causes the SPIR-V LLVM translator to behave the same as it did previously, as long as the extension is not enabled.
  2. I added a test for the case where the execution scope is only known at runtime. The test checks that the device barrier extension and capability are declared when the extension is enabled, and that the device barrier extension and capability are not declared when the extension is not enabled.

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