From b255ef068b77a45fdd0b595a555386928a61d56e Mon Sep 17 00:00:00 2001 From: jsmall-nvidia Date: Mon, 12 Jun 2023 14:55:44 -0400 Subject: Update shader-execution-reordering.md Fix comment which no longer applies. --- docs/shader-execution-reordering.md | 2 -- 1 file changed, 2 deletions(-) (limited to 'docs/shader-execution-reordering.md') diff --git a/docs/shader-execution-reordering.md b/docs/shader-execution-reordering.md index f6d44fcab..0ecb00c56 100644 --- a/docs/shader-execution-reordering.md +++ b/docs/shader-execution-reordering.md @@ -5,8 +5,6 @@ Slang provides preliminary support for Shader Execution Reordering (SER). The AP The feature is available on D3D12 via [NVAPI](nvapi-support.md) and on Vulkan through the [GL_NV_shader_invocation_reorder](https://github.com/KhronosGroup/GLSL/blob/master/extensions/nv/GLSL_NV_shader_invocation_reorder.txt) extension. -Note: An upgrade is required to `slang-glslang` and associated projects to add support for SPIR-V output via Slang. - ## Vulkan SER as implemented on Vulkan has extra limitations on usage. On D3D via NvAPI `HitObject` variables are like regular variables. They can be assigned, passed to functions and so forth. Using `GL_NV_shader_invocation_reorder` on Vulkan, this isn't the case and `HitObject` variables are special and act is if their introduction allocates a single unique entry. One implication of this is there are limitations on Vulkan around HitObject with flow control, and assignment to HitObject variables. -- cgit v1.2.3