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 June 28, 2021 Vulkan 1.2.183 spec update:
* Update release number to 183 for this update. Github Issues: * Rewrite and simplify the <<interfaces-iointerfaces-matching, Interface Matching>> section. Clarify that results are undefined if the size of a vector mismatches (public issue 666; internal issues 1269, 2059, 2323). * Remove inappropriate `const` from `void *pNext` members of `returnedonly` structures in `vk.xml` (public issue 1482, internal issue 2644). * Add a NOTE to the <<interfaces, Shader Interfaces>> chapter that SPIR-V execution model keywords with extension suffixes will always be present in spec builds, even in a build not supporting any extensions, since these keywords appear in the unified SPIR-V specification without such qualifiers (public issue 1483, internal issue 2621). * Modify `vk.xml` to include the Vulkan platform header via the path `vulkan/vk_platform.h` rather than just `vk_platform.h` (public pull request 1538). * Add length annotations for slink:VkCuLaunchInfoNVX (public issue 1548). * Describe slink:VkSubpassDescription::pname:pDepthStencilAttachment correctly as a pointer to a structure, not a pointer to an array of structures (public issue 1561). * Fix `structextends` attribute of slink:VkPhysicalDeviceRayTracingMotionBlurFeaturesNV, declare its pname:pNext member correctly, and fix some typos in the related extension language (public issue 1565, internal issue 2724). Internal Issues: * Add explicit valid usage statements for flink:vkCmdClearColorImage::slink:VkClearColorValue and slink:VkRenderPassBeginInfo::slink:VkClearValue (internal issue 2490). * Change the term "`vertex processing {shader} stage`" to "`pre-rasterization shader stage`" throughout the specification, link to a single definition, and add "`pre-rasterization`" to the glossary (internal issue 2634). * Add an `<implicitexternsync>` constraint for flink:vkResetCommandBuffers::pname:pool (internal issue 2646). * Fix typo `vkCmdResetEvent` -> `vkResetEvent` in flink:vkResetEvent valid usage statements (internal issue 2651). * Fix wording of scope dependencies for slink:VkMemoryBarrier2KHR, slink:VkBufferMemoryBarrier2KHR, and slink:VkImageMemoryBarrier2KHR members pname:srcAccessMask and pname:dstAccessMask (internal issue 2654). * Require support for pname:shaderInt64 in the <<features-requirements, Feature Requirements>> section when pname:atomicInt64 features are supported (internal issue 2660). * Clarify ray tracing valid usage statements for cases where a parameter refers to an acceleration structure that must have been built (internal issue 2715). * Add a NOTE clarifying shader record buffer uniformity in the <<shader-binding-table, Shader Binding Table>> section (internal issue 2719). * Minor clarifications and typo fixes to `<<VK_HUAWEI_subpass_shading>>` (internal issue 2722). * Add missing <spirvextension> entry in `vk.xml` to enable `SPV_KHR_subgroup_uniform_control_flow` (internal issue 2733). * Move SPIR-V valid usage statement from the <<spirvenv-module-validation-runtime, Runtime SPIR-V Validation>> section to <<spirvenv-module-validation-standalone]] Standalone SPIR-V Validation>> (internal merge request 4637). * Add a new <<spirvenv-image-signedness, Signedness of SPIR-V Image Accesses>> section to allow the use of unsigned Sampled Types with code:SignExtend and signed code:Format decorations (internal merge request 4638). * Add missing slink:VkDeviceCreateInfo to `structextends` attribute of slink:VkPhysicalDeviceGlobalPriorityQueryFeaturesEXT (internal merge request 4652). * Remove nonexistent pname:minFragmentSize from the <<limits-minmax, Limit Requirements>> table (internal merge request 4655). * Fix markup typo for `<<VK_NV_fragment_shader_barycentric>>` ifdef (internal merge request 4663).
- Loading branch information
Showing
29 changed files
with
507 additions
and
291 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
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.