Change log for November 2, 2021 Vulkan 1.2.197 spec update:

  * Update release number to 197 for this update.

Github Issues:

  * Align some of the provisional video standard headers enums and bitfields
    to have predictable sizes (public issue 1571).
  * Remove exporting of D3D memory handles from
    slink:VkExportMemoryWin32HandleInfoKHR (public pull request 1612).
  * Add language to slink:VkAccelerationStructureBuildGeometryInfoKHR
    explicitly stating that source and target acceleration structures are
    allowed to be the same or different during an update (public issue
    1641).
  * Fix typos (public pull request 1662).
  * Register remaining newly introduced `vk_video` types in `vk.xml` (public
    pull request 1663).

Internal Issues:

  * Clarify <<resources-external-sharing, ownership transfers on external
    resources>> (internal issue 2692).
  * Changes to (nearly) eliminate dead internal links and improve scripts:
  ** Correctly generate API dependencies on extensions and core versions in
     cases where "`spelling aliases`" were present
  ** Clean up a few incorrectly marked up links, anchors, and refpage block
     alias= attributes
  ** Use an API alias map to substitute promoted API names for promoted-to
     APIs when an older or restricted spec is being generated and the
     promoted-to API is not included
  * Tag sname:VkVideo{Encode,Decode}H26{4,5}ProfileEXT structures as
    extending slink:VkQueryPoolCreateInfo in `vk.xml` (internal issue 2861).
  * Grammar edits to slink:VkAccelerationStructureKHR (internal issue 2887).
  * Change the cited title of the <<LoaderInterfaceArchitecture>> document
    to "`Architecture of the Vulkan Loader Interfaces`" matching a recent
    change in KhronosGroup/Vulkan-Loader#685
    (internal merge request 4823).
  * Re-remove etext:VkVideoEncodeH265CapabilityFlagBitsEXT, which was
    accidentally reintroduced but is still unused (internal merge request
    4885).
  * Update wording for
    ename:VK_BUILD_ACCELERATION_STRUCTURE_ALLOW_UPDATE_BIT_KHR since it no
    longer contains `"update`" (internal merge request 4886).
  * Consistency edits to remove "`instance of`" when referring to a specific
    structure, and use "`render pass`" instead of "`renderpass`" as a noun
    (internal merge request 4896).
  * Add -version option to 'makeSpec' frontend build script.

New Extensions

  * `<<VK_KHR_dynamic_rendering>>`

ChangeLog.txt

@@ -11,6 +11,60 @@ public pull requests that have been accepted.
 
 -----------------------------------------------------
 
+Change log for November 2, 2021 Vulkan 1.2.197 spec update:
+
+  * Update release number to 197 for this update.
+
+Github Issues:
+
+  * Align some of the provisional video standard headers enums and bitfields
+    to have predictable sizes (public issue 1571).
+  * Remove exporting of D3D memory handles from
+    slink:VkExportMemoryWin32HandleInfoKHR (public pull request 1612).
+  * Add language to slink:VkAccelerationStructureBuildGeometryInfoKHR
+    explicitly stating that source and target acceleration structures are
+    allowed to be the same or different during an update (public issue
+    1641).
+  * Fix typos (public pull request 1662).
+  * Register remaining newly introduced `vk_video` types in `vk.xml` (public
+    pull request 1663).
+
+Internal Issues:
+
+  * Clarify <<resources-external-sharing, ownership transfers on external
+    resources>> (internal issue 2692).
+  * Changes to (nearly) eliminate dead internal links and improve scripts:
+  ** Correctly generate API dependencies on extensions and core versions in
+     cases where "`spelling aliases`" were present
+  ** Clean up a few incorrectly marked up links, anchors, and refpage block
+     alias= attributes
+  ** Use an API alias map to substitute promoted API names for promoted-to
+     APIs when an older or restricted spec is being generated and the
+     promoted-to API is not included
+  * Tag sname:VkVideo{Encode,Decode}H26{4,5}ProfileEXT structures as
+    extending slink:VkQueryPoolCreateInfo in `vk.xml` (internal issue 2861).
+  * Grammar edits to slink:VkAccelerationStructureKHR (internal issue 2887).
+  * Change the cited title of the <<LoaderInterfaceArchitecture>> document
+    to "`Architecture of the Vulkan Loader Interfaces`" matching a recent
+    change in https://github.com/KhronosGroup/Vulkan-Loader/pull/685
+    (internal merge request 4823).
+  * Re-remove etext:VkVideoEncodeH265CapabilityFlagBitsEXT, which was
+    accidentally reintroduced but is still unused (internal merge request
+    4885).
+  * Update wording for
+    ename:VK_BUILD_ACCELERATION_STRUCTURE_ALLOW_UPDATE_BIT_KHR since it no
+    longer contains `"update`" (internal merge request 4886).
+  * Consistency edits to remove "`instance of`" when referring to a specific
+    structure, and use "`render pass`" instead of "`renderpass`" as a noun
+    (internal merge request 4896).
+  * Add -version option to 'makeSpec' frontend build script.
+
+New Extensions
+
+  * `<<VK_KHR_dynamic_rendering>>`
+
+-----------------------------------------------------
+
 Change log for October 13, 2021 Vulkan 1.2.196 spec update:
 
   * Update release number to 196 for this update.

Makefile

@@ -120,7 +120,7 @@ VERBOSE =
 # ADOCOPTS options for asciidoc->HTML5 output
 
 NOTEOPTS     = -a editing-notes -a implementation-guide
-PATCHVERSION = 196
+PATCHVERSION = 197
 
 ifneq (,$(findstring VK_VERSION_1_2,$(VERSIONS)))
 SPECMINOR = 2

appendices/VK_EXT_conditional_rendering.txt

@@ -55,4 +55,4 @@ None.
 
   * Revision 2, 2018-05-21 (Vikram Kushwaha)
     - Add new pipeline stage, access flags and limit conditional rendering
-      to a subpass or entire renderpass.
+      to a subpass or entire render pass.

appendices/VK_EXT_provoking_vertex.txt

@@ -43,18 +43,18 @@ include::{generated}/interfaces/VK_EXT_provoking_vertex.txt[]
 
 1) At what granularity should this state be set?
 
-*RESOLVED*: At pipeline bind, with an optional per-renderpass restriction.
+*RESOLVED*: At pipeline bind, with an optional per-render pass restriction.
 
 The most natural place to put this state is in the graphics pipeline object.
 Some implementations require it to be known when creating the pipeline, and
 pipeline state is convenient for implementing OpenGL 3.2's
 glProvokingVertex, which can change the state between draw calls.
-However, some implementations can only change it approximately renderpass
+However, some implementations can only change it approximately render pass
 granularity.
 To accommodate both, provoking vertex will be pipeline state, but
-implementations can require that only one mode is used within a renderpass
-instance; the renderpass's mode is chosen implicitly when the first pipeline
-is bound.
+implementations can require that only one mode is used within a render pass
+instance; the render pass's mode is chosen implicitly when the first
+pipeline is bound.
 
 2) Does the provoking vertex mode affect the order that vertices are written
 to transform feedback buffers?

appendices/VK_KHR_create_renderpass2.txt

@@ -21,7 +21,7 @@ that can be easily extended by other extensions through the substructures of
 render pass creation.
 The Vulkan 1.0 render pass creation sub-structures do not include
 ptext:sType/ptext:pNext members.
-Additionally, the renderpass begin/next/end commands have been augmented
+Additionally, the render pass begin/next/end commands have been augmented
 with new extensible structures for passing additional subpass information.
 
 The slink:VkRenderPassMultiviewCreateInfo and

appendices/VK_KHR_dynamic_rendering.txt

@@ -0,0 +1,43 @@
+// Copyright 2017-2021 The Khronos Group, Inc.
+//
+// SPDX-License-Identifier: CC-BY-4.0
+
+include::{generated}/meta/{refprefix}VK_KHR_dynamic_rendering.txt[]
+
+=== Other Extension Metadata
+
+*Last Modified Date*::
+    2021-10-06
+*Contributors*::
+  - Tobias Hector, AMD
+  - Arseny Kapoulkine, Roblox
+  - François Duranleau, Gameloft
+  - Stuart Smith, AMD
+  - Hai Nguyen, Google
+  - Jean-François Roy, Google
+  - Jeff Leger, Qualcomm
+  - Jan-Harald Fredriksen, Arm
+  - Piers Daniell, Nvidia
+  - James Fitzpatrick, Imagination
+  - Piotr Byszewski, Mobica
+  - Jesse Hall, Google
+  - Mike Blumenkrantz, Valve
+
+=== Description
+
+This extension allows applications to create single-pass render pass
+instances without needing to create render pass objects or framebuffers.
+Dynamic render passes can also span across multiple primary command buffers,
+rather than relying on secondary command buffers.
+
+This extension also incorporates ename:VK_ATTACHMENT_STORE_OP_NONE_KHR from
+<<VK_QCOM_render_pass_store_ops,VK_QCOM_render_pass_store_ops>>, enabling
+applications to avoid unnecessary synchronization when an attachment is not
+written during a render pass.
+
+include::{generated}/interfaces/VK_KHR_dynamic_rendering.txt[]
+
+=== Version History
+
+  * Revision 1, 2021-10-06 (Tobias Hector)
+    - Initial revision

appendices/VK_NVX_binary_import.txt

@@ -22,6 +22,10 @@ include::{generated}/interfaces/VK_NVX_binary_import.txt[]
 endif::EXTENSION_UNDEFINED[]
 
 ifndef::EXTENSION_UNDEFINED[]
+// The anchor is added here as a landing place for a reference from
+// the autogenerated section of the features chapter, until spec
+// language is written.
+[[vkCmdCuLaunchKernelNVX]]
 [NOTE]
 .Note
 ====

appendices/VK_QCOM_render_pass_shader_resolve.txt

@@ -57,7 +57,7 @@ While this may not be a common use case, and while most fixed-function
 resolve hardware has this limitation, there is little reason to require a
 shader resolve to resolve to a single sample buffer.
 
-3) Should a shader resolve subpass be the last subpass in a renderpass?
+3) Should a shader resolve subpass be the last subpass in a render pass?
 
 *RESOLVED* Yes.
 

appendices/VK_QCOM_render_pass_store_ops.txt

@@ -13,7 +13,7 @@ include::{generated}/meta/{refprefix}VK_QCOM_render_pass_store_ops.txt[]
 
 === Description
 
-Renderpass attachments can: be read-only for the duration of a renderpass.
+Renderpass attachments can: be read-only for the duration of a render pass.
 
 Examples include input attachments and depth attachments where depth tests
 are enabled but depth writes are not enabled.

appendices/VK_QCOM_rotated_copy_commands.txt

@@ -21,7 +21,7 @@ flink:vkCmdCopyBufferToImage2KHR.
 When copying between two resources, where one resource contains rotated
 content and the other does not, a rotated copy may be desired.
 This extension may be used in combination with VK_QCOM_render_pass_transform
-which adds rotated renderpasses.
+which adds rotated render passes.
 
 This extension adds an extension structure to the following commands:
 vkCmdBlitImage2KHR, vkCmdCopyImageToBuffer2KHR and

chapters/VK_INTEL_performance_query/queries.txt

@@ -136,13 +136,15 @@ elink:VkPerformanceValueTypeINTEL value.
 include::{generated}/validity/structs/VkPerformanceValueDataINTEL.txt[]
 --
 
-[open,refpage='VkQueryPoolPerformanceQueryCreateInfoINTEL',desc='Structure specifying parameters to create a pool of performance queries',type='structs']
+[open,refpage='VkQueryPoolPerformanceQueryCreateInfoINTEL',desc='Structure specifying parameters to create a pool of performance queries',type='structs',alias='VkQueryPoolCreateInfoINTEL']
 --
 The sname:VkQueryPoolPerformanceQueryCreateInfoINTEL structure is defined
 as:
 
 include::{generated}/api/structs/VkQueryPoolPerformanceQueryCreateInfoINTEL.txt[]
 
+include::{generated}/api/structs/VkQueryPoolCreateInfoINTEL.txt[]
+
 To create a pool for Intel performance queries, set
 slink:VkQueryPoolCreateInfo::pname:queryType to
 ename:VK_QUERY_TYPE_PERFORMANCE_QUERY_INTEL and add a

chapters/VK_KHR_swapchain/PresentId.txt

@@ -53,8 +53,8 @@ presentation of the first pixel in the new image to the user.
   * [[VUID-VkPresentIdKHR-swapchainCount-04998]]
     pname:swapchainCount must: be the same value as
     sname:VkPresentInfoKHR::pname:swapchainCount, where this
-    sname:VkPresentIdKHR is in the pNext-chain of the sname:VkPresentInfoKHR
-    structure
+    sname:VkPresentIdKHR is in the pname:pNext chain of the
+    sname:VkPresentInfoKHR structure
   * [[VUID-VkPresentIdKHR-presentIds-04999]]
     Each pname:presentIds entry must: be greater than any previous
     pname:presentIds entry passed for the associated pname:pSwapchains entry

chapters/VK_NV_device_generated_commands/generation.txt

@@ -13,7 +13,7 @@ execution state call:
 include::{generated}/api/protos/vkGetGeneratedCommandsMemoryRequirementsNV.txt[]
 
   * pname:device is the logical device that owns the buffer.
-  * pname:pInfo is a pointer to an instance of the
+  * pname:pInfo is a pointer to a
     sname:VkGeneratedCommandsMemoryRequirementsInfoNV structure containing
     parameters required for the memory requirements query.
   * pname:pMemoryRequirements is a pointer to a slink:VkMemoryRequirements2
@@ -74,7 +74,7 @@ include::{generated}/api/protos/vkCmdExecuteGeneratedCommandsNV.txt[]
     preprocessed on the device.
     If it is ename:VK_FALSE this command will implicitly trigger the
     preprocessing step, otherwise not.
-  * pname:pGeneratedCommandsInfo is a pointer to an instance of the
+  * pname:pGeneratedCommandsInfo is a pointer to a
     slink:VkGeneratedCommandsInfoNV structure containing parameters
     affecting the generation of commands.
 
@@ -265,7 +265,7 @@ Commands can: be preprocessed prior execution using the following command:
 include::{generated}/api/protos/vkCmdPreprocessGeneratedCommandsNV.txt[]
 
   * pname:commandBuffer is the command buffer which does the preprocessing.
-  * pname:pGeneratedCommandsInfo is a pointer to an instance of the
+  * pname:pGeneratedCommandsInfo is a pointer to a
     slink:VkGeneratedCommandsInfoNV structure containing parameters
     affecting the preprocessing step.
 

chapters/VK_NV_device_generated_commands/indirectcommands.txt

@@ -24,7 +24,7 @@ include::{generated}/api/protos/vkCreateIndirectCommandsLayoutNV.txt[]
 
   * pname:device is the logical device that creates the indirect command
     layout.
-  * pname:pCreateInfo is a pointer to an instance of the
+  * pname:pCreateInfo is a pointer to a
     sname:VkIndirectCommandsLayoutCreateInfoNV structure containing
     parameters affecting creation of the indirect command layout.
   * pname:pAllocator controls host memory allocation as described in the

chapters/accelstructures.txt

@@ -509,6 +509,13 @@ motion in its instances must: set
 ename:VK_BUILD_ACCELERATION_STRUCTURE_MOTION_BIT_NV in pname:flags.
 endif::VK_NV_ray_tracing_motion_blur[]
 
+Members pname:srcAccelerationStructure and pname:dstAccelerationStructure
+may: be the same or different for an update operation (when pname:mode is
+ename:VK_BUILD_ACCELERATION_STRUCTURE_MODE_UPDATE_KHR).
+If they are the same, the update happens in-place.
+Otherwise, the target acceleration structure is updated and the source is
+not modified.
+
 .Valid Usage
 ****
   * [[VUID-VkAccelerationStructureBuildGeometryInfoKHR-type-03654]]