The time when SPIR-V was an ancillary part of the compiler is past. We have enabled SPIR-V with our official releases for over a year. We have announced our intent to switch to SPIR-V.
Is your feature request related to a problem? Please describe.
The ability to disable SPIR-V gives us a different build configuration that we don't test in automation, which can result in committing changes that disrupt developers who haven't enabled SPIR-V.
Describe the solution you'd like
Remove the ability to disable SPIR-V. This will simplify a lot of configurations and give us a consistent build target. Additionally, those who disable it locally won't find breakages only when they upload the code.
Describe alternatives you've considered
We could add a spirv-disabled build to automation.
The time when SPIR-V was an ancillary part of the compiler is past. We have enabled SPIR-V with our official releases for over a year. We have announced our intent to switch to SPIR-V.
Is your feature request related to a problem? Please describe.
The ability to disable SPIR-V gives us a different build configuration that we don't test in automation, which can result in committing changes that disrupt developers who haven't enabled SPIR-V.
Describe the solution you'd like
Remove the ability to disable SPIR-V. This will simplify a lot of configurations and give us a consistent build target. Additionally, those who disable it locally won't find breakages only when they upload the code.
Describe alternatives you've considered
We could add a spirv-disabled build to automation.