[SYCL][Doc] Add OpDeviceRegistryVersionINTEL; Misc changes #19883
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds
OpDeviceRegistryVersionINTELto specify which version of the device registry was used when producing a module. This allows a consumer to correctly interpretOpSpecConstantArchitectureINTELandOpSpecConstantTargetINTELinstructions without any knowledge about the producer. Currently, the producer implemented in SPIRV-Tools adds anOpModuleProcessednote with the version, but since the version carries a semantic information (ie. determines the result of theOpSpecConstantArchitecture/TargetINTELinstructions), I think it should be a separate, non-debug, instruction.Other changes:
OpSpecConstantTargetINTEL.OpExtInstwithConditionalINTELbecause it can be in the types section outside a function in the case of non-semantic instructions.To be merged after #19782