forked from KhronosGroup/Vulkan-Docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Change log for May 24, 2022 Vulkan 1.3.215 spec update:
* Update release number to 215 for this update. Public Issues: * Fix markup error to make slink:VkImageResolve2 appear right after slink:VkImageResolve, rather than appearing in the next section (public pull request 1856). Internal Issues: * Allow slink:VkDescriptorPoolCreateInfo::pname:poolSizeCount to be `0` in `vk.xml` (internal issue #2974). * Add valid usage statements to flink:vkCmdExecuteCommands requiring that the depth or stencil format in slink:VkCommandBufferInheritanceRenderingInfo must be ename:VK_FORMAT_UNDEFINED if a `NULL` attachment is used (internal issue 3016). * Remove (incomplete) list of SPIR-V decorations from intro of interface matching chapter (internal issue 3043). * Add valid usage statement disallowing VkImageDrmFormatModifierExplicitCreateInfoEXT in the pname:pNext chain of slink:VkDeviceImageMemoryRequirementsKHR (internal issue #3051). * Add missing references to flink:vkQueueSubmit2 in the <<synchronization-fences-signaling>> and <<synchronization-semaphores-signaling, Semaphore Signaling>> sections (internal issue #3077). * Clarify that pipeline libraries can link against other libraries following the description of slink:VkPipelineLibraryCreateInfoKHR (internal issue #3083). * Fix suffix of some SPIR-V tokens to `AMD` for apiext:VK_AMD_shader_early_and_late_fragment_tests (internal merge request #5199). New Extensions: * apiext:VK_KHR_fragment_shader_barycentric
- Loading branch information
Showing
19 changed files
with
503 additions
and
135 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,80 @@ | ||
// Copyright 2018-2022 The Khronos Group Inc. | ||
// | ||
// SPDX-License-Identifier: CC-BY-4.0 | ||
|
||
include::{generated}/meta/{refprefix}VK_KHR_fragment_shader_barycentric.txt[] | ||
|
||
=== Other Extension Metadata | ||
|
||
*Last Modified Date*:: | ||
2022-03-10 | ||
*IP Status*:: | ||
No known IP claims. | ||
*Interactions and External Dependencies*:: | ||
- This extension requires | ||
{spirv}/KHR/SPV_KHR_fragment_shader_barycentric.html[`SPV_KHR_fragment_shader_barycentric`] | ||
- This extension provides API support for | ||
https://github.com/KhronosGroup/GLSL/blob/master/extensions/ext/GLSL_EXT_fragment_shader_barycentric.txt[`GL_EXT_fragment_shader_barycentric`] | ||
*Contributors*:: | ||
- Stu Smith, AMD | ||
- Tobias Hector, AMD | ||
- Graeme Leese, Broadcom | ||
- Jan-Harald Fredriksen, Arm | ||
- Slawek Grajewski, Intel | ||
- Pat Brown, NVIDIA | ||
- Hans-Kristian Arntzen, Valve | ||
- Contributors to the VK_NV_fragment_shader_barycentric specification | ||
|
||
|
||
=== Description | ||
|
||
This extension is based on the `<<VK_NV_fragment_shader_barycentric>>` | ||
extension, and adds support for the following SPIR-V extension in Vulkan: | ||
|
||
* {spirv}/KHR/SPV_KHR_fragment_shader_barycentric.html[`SPV_KHR_fragment_shader_barycentric`] | ||
|
||
The extension provides access to three additional fragment shader variable | ||
decorations in SPIR-V: | ||
|
||
* code:PerVertexKHR, which indicates that a fragment shader input will not | ||
have interpolated values, but instead must be accessed with an extra | ||
array index that identifies one of the vertices of the primitive | ||
producing the fragment | ||
* code:BaryCoordKHR, which indicates that the variable is a | ||
three-component floating-point vector holding barycentric weights for | ||
the fragment produced using perspective interpolation | ||
* code:BaryCoordNoPerspKHR, which indicates that the variable is a | ||
three-component floating-point vector holding barycentric weights for | ||
the fragment produced using linear interpolation | ||
|
||
When using GLSL source-based shader languages, the following variables from | ||
`GL_EXT_fragment_shader_barycentric` map to these SPIR-V built-in | ||
decorations: | ||
|
||
* `in vec3 gl_BaryCoordEXT;` -> code:BaryCoordKHR | ||
* `in vec3 gl_BaryCoordNoPerspEXT;` -> code:BaryCoordNoPerspKHR | ||
|
||
GLSL variables declared using the code:pervertexEXT GLSL qualifier are | ||
expected to be decorated with code:PerVertexKHR in SPIR-V. | ||
|
||
include::{generated}/interfaces/VK_KHR_fragment_shader_barycentric.txt[] | ||
|
||
=== New Built-In Variables | ||
|
||
* <<interfaces-builtin-variables-barycoordkhr,code:BaryCoordKHR>> | ||
* <<interfaces-builtin-variables-barycoordnoperspkhr,code:BaryCoordNoPerspKHR>> | ||
|
||
=== New SPIR-V Decorations | ||
|
||
* <<shaders-interpolation-decorations-pervertexkhr,code:PerVertexKHR>> | ||
|
||
=== New SPIR-V Capabilities | ||
|
||
* <<spirvenv-capabilities-table-FragmentBarycentricKHR,code:FragmentBarycentricKHR>> | ||
|
||
=== Issues | ||
|
||
=== Version History | ||
|
||
* Revision 1, 2022-03-10 (Stu Smith) | ||
- Initial revision |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.