Change log for May 10, 2024 Vulkan 1.3.285 spec update:

Public Issues

  * Update VkMemoryMapInfoKHR VUs to not require VK_WHOLE_SIZE with
    VK_MEMORY_MAP_PLACED_BIT (public issue 2350).
  * Add a <<fundamentals-strings, String Representation>> section and
    clarify that fixed-length string buffers in API structures always
    include the null terminator (public issue 2351).
  * Update refpage short descriptions of VkAttachmentLoad/StoreOp to be
    consistent with spec language (public issue 2353).
  * Clarify that the KHR and EXT load_store_op_none extensions were not
    promoted to Vulkan 1.3 (public PR 2357).

Internal Issues

  * Add a VkGraphicsPipelineCreateInfo VU banning "`read-only`" input
    attachments without VkRenderingInputAttachmentIndexInfoKHR (internal
    issue 3862).
  * Add explicit reference to RayQueryPositionFetchKHR SPIR-V capability in
    the VK_KHR_ray_tracing_position_fetch extension appendix and XML
    spirvcapability tags (internal MR 6617).
  * Remove MaximallyReconvergesKHR capability (which is not a capability,
    but an execution mode) from XML (internal MR 6618).
  * Add alias and enum value-> type maps in `reg.py` (internal MR 6620).
  * Add missing shader object VU for vkCmdDispatchBase (internal MR 6623).
  * Make build tests less sensitive to asciidoctor versions and CSS changes
    by just comparing HTML body content (internal MR 6637).
  * Do not allow overlapping builtin decorations for an entry point in the
    <<interfaces-builtin-variables, Built-In Variables>> section, and add
    some related <<spirvenv-module-validation-standalone, Standalone SPIR-V
    Validation>> VUs (KhronosGroup/SPIRV-Cross issue 2313).

New Extensions

  * VK_MESA_image_alignment_control

ChangeLog.adoc

@@ -14,6 +14,45 @@ appears frequently in the change log.
 
 '''
 
+Change log for May 10, 2024 Vulkan 1.3.285 spec update:
+
+Public Issues
+
+  * Update VkMemoryMapInfoKHR VUs to not require VK_WHOLE_SIZE with
+    VK_MEMORY_MAP_PLACED_BIT (public issue 2350).
+  * Add a <<fundamentals-strings, String Representation>> section and
+    clarify that fixed-length string buffers in API structures always
+    include the null terminator (public issue 2351).
+  * Update refpage short descriptions of VkAttachmentLoad/StoreOp to be
+    consistent with spec language (public issue 2353).
+  * Clarify that the KHR and EXT load_store_op_none extensions were not
+    promoted to Vulkan 1.3 (public PR 2357).
+
+Internal Issues
+
+  * Add a VkGraphicsPipelineCreateInfo VU banning "`read-only`" input
+    attachments without VkRenderingInputAttachmentIndexInfoKHR (internal
+    issue 3862).
+  * Add explicit reference to RayQueryPositionFetchKHR SPIR-V capability in
+    the VK_KHR_ray_tracing_position_fetch extension appendix and XML
+    spirvcapability tags (internal MR 6617).
+  * Remove MaximallyReconvergesKHR capability (which is not a capability,
+    but an execution mode) from XML (internal MR 6618).
+  * Add alias and enum value-> type maps in `reg.py` (internal MR 6620).
+  * Add missing shader object VU for vkCmdDispatchBase (internal MR 6623).
+  * Make build tests less sensitive to asciidoctor versions and CSS changes
+    by just comparing HTML body content (internal MR 6637).
+  * Do not allow overlapping builtin decorations for an entry point in the
+    <<interfaces-builtin-variables, Built-In Variables>> section, and add
+    some related <<spirvenv-module-validation-standalone, Standalone SPIR-V
+    Validation>> VUs (KhronosGroup/SPIRV-Cross issue 2313).
+
+New Extensions
+
+  * VK_MESA_image_alignment_control
+
+'''
+
 Change log for May 5, 2024 Vulkan 1.3.284 spec update:
 
 Public Issues

Makefile

@@ -138,7 +138,7 @@ VERBOSE =
 # ADOCOPTS options for asciidoc->HTML5 output
 
 NOTEOPTS     = -a editing-notes -a implementation-guide
-PATCHVERSION = 284
+PATCHVERSION = 285
 BASEOPTS     =
 
 ifneq (,$(findstring VKSC_VERSION_1_0,$(VERSIONS)))

appendices/VK_KHR_ray_tracing_position_fetch.adoc

@@ -48,6 +48,7 @@ include::{generated}/interfaces/VK_KHR_ray_tracing_position_fetch.adoc[]
 === New SPIR-V Capabilities
 
   * <<spirvenv-capabilities-table-RayTracingPositionFetchKHR,RayTracingPositionFetchKHR>>
+  * <<spirvenv-capabilities-table-RayQueryPositionFetchKHR,RayQueryPositionFetchKHR>>
 
 === Issues
 

appendices/VK_KHR_shader_maximal_reconvergence.adoc

@@ -36,10 +36,6 @@ other tangled instructions.
 
 include::{generated}/interfaces/VK_KHR_shader_maximal_reconvergence.adoc[]
 
-=== New SPIR-V Capabilities
-
-  * <<spirvenv-capabilities-table-MaximallyReconvergesKHR,MaximallyReconvergesKHR>>
-
 === Version History
 
 * Revision 1, 2021-11-12 (Alan Baker)

appendices/VK_MESA_image_alignment_control.adoc

@@ -0,0 +1,46 @@
+// Copyright 2024 The Khronos Group Inc.
+//
+// SPDX-License-Identifier: CC-BY-4.0
+
+include::{generated}/meta/{refprefix}VK_MESA_image_alignment_control.adoc[]
+
+=== Other Extension Metadata
+
+*Last Modified Date*::
+    2024-05-03
+*IP Status*::
+    No known IP claims.
+*Contributors*::
+  - Hans-Kristian Arntzen, Valve
+
+=== Description
+
+This extension allows applications to request a narrower alignment for
+images than an implementation would otherwise require.
+Some implementations internally support multiple image layouts in
+ename:VK_IMAGE_TILING_OPTIMAL, each with different alignment requirements
+and performance trade-offs.
+In some API layering use cases such as D3D12, it is beneficial to be able to
+control the alignment, since certain alignments for placed resources are
+guaranteed to be supported, and emulating that expectation requires
+unnecessary padding of allocations.
+
+slink:VkImageAlignmentControlCreateInfoMESA can: be chained to
+slink:VkImageCreateInfo, requesting that the alignment is no more than the
+provided alignment.
+If the requested alignment is not supported for a given
+slink:VkImageCreateInfo, a larger alignment may: be returned.
+
+While something similar could be achieved with
+`apiext:VK_EXT_image_drm_format_modifier` in theory, this is not the
+intended way to use that extension.
+Format modifiers are generally used for externally shareable images, and
+would not be platform portable.
+It is also a cumbersome API to use just to lower the alignment.
+
+include::{generated}/interfaces/VK_MESA_image_alignment_control.adoc[]
+
+=== Version History
+
+  * Revision 1, 2024-04-05 (Hans-Kristian Arntzen)
+  ** Initial specification

appendices/spirvenv.adoc

@@ -330,6 +330,12 @@ or knowledge of runtime information, such as enabled features.
   * [[VUID-{refpage}-BuiltIn-04668]]
     Any code:BuiltIn decoration not listed in
     <<interfaces-builtin-variables>> must: not be used
+  * [[VUID-{refpage}-OpEntryPoint-09658]]
+    For a given code:OpEntryPoint, any code:BuiltIn decoration must: not be
+    used more than once by the code:Input interface.
+  * [[VUID-{refpage}-OpEntryPoint-09659]]
+    For a given code:OpEntryPoint, any code:BuiltIn decoration must: not be
+    used more than once by the code:Output interface.
   * [[VUID-{refpage}-Location-06672]]
     The code:Location or code:Component decorations must: only be used with
     the code:Input, code:Output, code:RayPayloadKHR,

build_tests/README.adoc

@@ -37,9 +37,9 @@ succeed but the output does not match the expectations, the diff is output for
 investigation.
 
 In some cases, the diff is small enough to be verified. Otherwise, each output
-in `gen-<build>/` needs to be manually reviewed to ensure the results are still
-correct; for example because the html is styled differently and the differences
-are as expected.
+in `gen-<build>/out/html/vkspec.html` needs to be manually reviewed to ensure
+the results are still correct; for example because the html is styled
+differently and the differences are as expected.
 
 If the mismatch between the output and expectations is expected, and the output
 is verified to be correct, update the expectations with: