1// Copyright 2017-2022 The Khronos Group Inc. 2// 3// SPDX-License-Identifier: CC-BY-4.0 4 5include::{generated}/meta/{refprefix}VK_KHR_pipeline_executable_properties.adoc[] 6 7=== Other Extension Metadata 8 9*Last Modified Date*:: 10 2019-05-28 11*IP Status*:: 12 No known IP claims. 13*Interactions and External Dependencies*:: 14*Contributors*:: 15 - Jason Ekstrand, Intel 16 - Ian Romanick, Intel 17 - Kenneth Graunke, Intel 18 - Baldur Karlsson, Valve 19 - Jesse Hall, Google 20 - Jeff Bolz, Nvidia 21 - Piers Daniel, Nvidia 22 - Tobias Hector, AMD 23 - Jan-Harald Fredriksen, ARM 24 - Tom Olson, ARM 25 - Daniel Koch, Nvidia 26 - Spencer Fricke, Samsung 27 28=== Description 29 30When a pipeline is created, its state and shaders are compiled into zero or 31more device-specific executables, which are used when executing commands 32against that pipeline. 33This extension adds a mechanism to query properties and statistics about the 34different executables produced by the pipeline compilation process. 35This is intended to be used by debugging and performance tools to allow them 36to provide more detailed information to the user. 37Certain compile-time shader statistics provided through this extension may 38be useful to developers for debugging or performance analysis. 39 40include::{generated}/interfaces/VK_KHR_pipeline_executable_properties.adoc[] 41 42=== Issues 43 441) What should we call the pieces of the pipeline which are produced by the 45compilation process and about which you can query properties and statistics? 46 47*RESOLVED*: Call them "`executables`". 48The name "`binary`" was used in early drafts of the extension but it was 49determined that "`pipeline binary`" could have a fairly broad meaning (such 50as a binary serialized form of an entire pipeline) and was too big of a 51namespace for the very specific needs of this extension. 52 53 54=== Version History 55 56 * Revision 1, 2019-05-28 (Jason Ekstrand) 57 ** Initial draft 58