Eliminate use of Vulkan header BEGIN_RANGE/END_RANGE/RANGE_SIZE enums
As per Khronos, these enums will no longer be available in future Vulkan headers:
https://www.khronos.org/news/permalink/khronos-group-asking-for-feedback-on-removing-begin-range-end-range-range-size-tokens-from-headers
This change now asserts that our Vulkan driver is built using a known
version of the Vulkan headers (vk::SwiftShaderVulkanHeaderVersion), and
when we update, the static assert will trip, reminding us to validate
the range constants that we use, and must manually maintain.
Bug: b/153337629
Bug: b/154215163
Change-Id: I319978e3979893a8a0cc44caf6cc79a584e518fb
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/44388Tested-by:
Antonio Maiorano <amaiorano@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
Showing
Please
register
or
sign in
to comment