Change log for August 11, 2019 Vulkan 1.1.119 spec update:

  * Update release number to 119.
  * A new extension was accidentally left out of the 1.1.118 spec update.
    This update corrects that oversight.

New Extensions:

  * `<<VK_KHR_pipeline_executable_properties>>`

ChangeLog.txt

@@ -8,6 +8,18 @@ public pull requests that have been accepted.
 
 -----------------------------------------------------
 
+Change log for August 11, 2019 Vulkan 1.1.119 spec update:
+
+  * Update release number to 119.
+  * A new extension was accidentally left out of the 1.1.118 spec update.
+    This update corrects that oversight.
+
+New Extensions:
+
+  * `<<VK_KHR_pipeline_executable_properties>>`
+
+-----------------------------------------------------
+
 Change log for August 11, 2019 Vulkan 1.1.118 spec update:
 
   * Update release number to 118.

Makefile

@@ -121,7 +121,7 @@ VERBOSE =
 # ADOCOPTS options for asciidoc->HTML5 output
 
 NOTEOPTS     = -a editing-notes -a implementation-guide
-PATCHVERSION = 118
+PATCHVERSION = 119
 ifneq (,$(findstring VK_VERSION_1_1,$(VERSIONS)))
 SPECREVISION = 1.1.$(PATCHVERSION)
 else

appendices/VK_KHR_pipeline_executable_properties.txt

@@ -0,0 +1,80 @@
+include::meta/VK_KHR_pipeline_executable_properties.txt[]
+
+*Last Modified Date*::
+    2019-05-28
+*IP Status*::
+    No known IP claims.
+*Interactions and External Dependencies*::
+*Contributors*::
+  - Jason Ekstrand, Intel
+  - Ian Romanick, Intel
+  - Kenneth Graunke, Intel
+  - Baldur Karlsson, Valve
+  - Jesse Hall, Google
+  - Jeff Bolz, Nvidia
+  - Piers Daniel, Nvidia
+  - Tobias Hector, AMD
+  - Jan-Harald Fredriksen, ARM
+  - Tom Olson, ARM
+  - Daniel Koch, Nvidia
+  - Spencer Fricke, Samsung
+
+When a pipeline is created, its state and shaders are compiled into zero or
+more device-specific executables, which are used when executing commands
+against that pipeline.
+This extension adds a mechanism to query properties and statistics about the
+different executables produced by the pipeline compilation process.
+This is intended to be used by debugging and performance tools to allow them
+to provide more detailed information to the user.
+Certain compile-time shader statistics provided through this extension may
+be useful to developers for debugging or performance analysis.
+
+=== New Enum Constants
+
+  * Extending elink:VkStructureType:
+  ** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_PIPELINE_EXECUTABLE_PROPERTIES_FEATURES_KHR
+  ** ename:VK_STRUCTURE_TYPE_PIPELINE_INFO_KHR
+  ** ename:VK_STRUCTURE_TYPE_PIPELINE_EXECUTABLE_PROPERTIES_KHR
+  ** ename:VK_STRUCTURE_TYPE_PIPELINE_EXECUTABLE_INFO_KHR
+  ** ename:VK_STRUCTURE_TYPE_PIPELINE_EXECUTABLE_STATISTIC_KHR
+  ** ename:VK_STRUCTURE_TYPE_PIPELINE_EXECUTABLE_INTERNAL_REPRESENTATION_KHR
+  * Extending elink:VkPipelineCreateFlagBits:
+  ** ename:VK_PIPELINE_CREATE_CAPTURE_STATISTICS_BIT_KHR
+  ** ename:VK_PIPELINE_CREATE_CAPTURE_INTERNAL_REPRESENTATIONS_BIT_KHR
+
+=== New Enums
+
+  * elink:VkPipelineExecutableStatisticFormatKHR
+
+=== New Structures
+
+  * slink:VkPhysicalDevicePipelineExecutablePropertiesFeaturesKHR
+  * slink:VkPipelineInfoKHR
+  * slink:VkPipelineExecutablePropertiesKHR
+  * slink:VkPipelineExecutableInfoKHR
+  * slink:VkPipelineExecutableStatisticValueKHR
+  * slink:VkPipelineExecutableStatisticKHR
+  * slink:VkPipelineExecutableInternalRepresentationKHR
+
+=== New Functions
+
+  * flink:vkGetPipelineExecutablePropertiesKHR
+  * flink:vkGetPipelineExecutableStatisticsKHR
+  * flink:vkGetPipelineExecutableInternalRepresentationsKHR
+
+=== Issues
+
+1) What should we call the pieces of the pipeline which are produced by the
+compilation process and about which you can query properties and statistics?
+
+*RESOLVED*: Call them "executables".
+The name "binary" was used in early drafts of the extension but it was
+determined that "pipeline binary" could have a fairly broad meaning (such as
+a binary serialized form of an entire pipeline) and was too big of a
+namespace for the very specific needs of this extension.
+
+
+=== Version History
+
+  * Revision 1, 2019-05-28 (Jason Ekstrand)
+    - Initial draft

chapters/VK_AMD_shader_info.txt

@@ -1,8 +1,5 @@
 // This section is included inside the Pipelines chapter (pipelines.txt)
 
-[[pipelines-shader-information]]
-== Pipeline Shader Information
-
 [open,refpage='vkGetShaderInfoAMD',desc='Get information about a shader in a pipeline',type='protos']
 --