Avoid invalid hit kinds with OpReportIntersection
authorRicardo Garcia <rgarcia@igalia.com>
Tue, 3 Nov 2020 08:17:17 +0000 (09:17 +0100)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Thu, 5 Nov 2020 14:46:20 +0000 (09:46 -0500)
commit52ade93e9dc2686d83554ce9000c27ab692613c2
tree3597e7d0aec7206f9eac9390de5c3639b9851807
parent875a15018865dbf171d3ca0ba7292346fb1b6739
Avoid invalid hit kinds with OpReportIntersection

OpReportIntersectionKHR accepts values in the [0, 127] range for the hit kind,
while gl_HitKindFrontFacingTriangleEXT or gl_HitKindBackFacingTriangleEXT are
reserved values outside that range and should not be used with
reportIntersectionEXT() in GLSL.

Affected tests:
dEQP-VK.ray_tracing_pipeline.builtin.*
dEQP-VK.ray_tracing_pipeline.memguarantee.*
dEQP-VK.ray_tracing_pipeline.complexcontrolflow.*

Components: Vulkan
VK-GL-CTS issue: 2626

Change-Id: Ic69abbb53968036ab56ebad4a832485fbccd8fb5
external/vulkancts/modules/vulkan/ray_tracing/vktRayTracingBuiltinTests.cpp
external/vulkancts/modules/vulkan/ray_tracing/vktRayTracingComplexControlFlowTests.cpp
external/vulkancts/modules/vulkan/ray_tracing/vktRayTracingMemGuaranteeTests.cpp