mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-05 02:53:57 +00:00
df88ded281
* Bump API patch number and header version number to 60 for this update.
Github Issues:
* Document that <<queries-timestamps, Timestamp Queries>> can only be
meaningfully compared when they are written from the same queue (public
issue 216).
* Document that the `<extension>` tag `type` attribute is required for
non-disabled extensions (derived from, but does not close public issue
354).
* Clean up registry schema length attribute descriptions to be consistent
and correct (public issue 555).
Internal Issues:
* Replace as much of the hand-written extension appendix metadata as
possible with asciidoc includes generated from corresponding attributes
of +vk.xml+, and enhance the style guide to match. This avoids
inconsistencies between +vk.xml+ and the appendices, and produces a more
uniform style (internal issue 137).
* Remove the generated extDependency.{py,sh} files from the tree and
create them dynamically on demand instead, reducing merge conflicts
(internal issue 713).
* Add a prototype tool for generating in-place difference markup for
sections guarded by asciidoc conditionals, and new syntax for open
blocks to support it (internal issue 833).
* Remove unnecessary restriction of etext:*SYNC_FD_BIT_KHR external handle
types to the same physical device in the
slink:VkPhysicalDeviceIDPropertiesKHR,
flink:VkImportMemoryWin32HandleInfoKHR,
slink:VkImportFenceWin32HandleInfoKHR, slink:VkImportFenceFdInfoKHR,
slink:VkImportSemaphoreWin32HandleInfoKHR,
slink:VkImportSemaphoreFdInfoKHR
<<external-memory-handle-types-compatibility, External memory handle
types compatibility>>, <<external-semaphore-handle-types-compatibility,
External semaphore handle types compatibility>>, and
<<external-fence-handle-types-compatibility, External fence handle types
compatibility>> sections (internal issue 956).
Other Issues:
* Remove dependency of +VK_KHX_device_group+ on +VK_KHR_swapchain+ (there
is an interaction, but not a strict dependency), and add a new
`extension` attribute to the `<require` XML tag to allow classifying a
subset of interfaces of an extension as requiring another extension.
Update the registry schema and documentation accordingly.
New Extensions:
* `VK_AMD_shader_fragment_mask` (and related `GL_AMD_shader_fragment_mask`
GLSL extension)
* `VK_EXT_sample_locations`
* `VK_EXT_validation_cache`
56 lines
1.4 KiB
Plaintext
56 lines
1.4 KiB
Plaintext
include::meta/VK_EXT_validation_cache.txt[]
|
|
*Last Modified Date*::
|
|
2017-08-29
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Contributors*::
|
|
- Cort Stratton, Google
|
|
- Chris Forbes, Google
|
|
|
|
This extension provides a mechanism for caching the results of potentially
|
|
expensive internal validation operations across multiple runs of a Vulkan
|
|
application.
|
|
At the core is the slink:VkValidationCacheEXT object type, which is managed
|
|
similarly to the existing slink:VkPipelineCache.
|
|
|
|
The new struct slink:VkShaderModuleValidationCacheCreateInfoEXT can be
|
|
included in the pname:pNext chain at flink:vkCreateShaderModule time.
|
|
It contains a slink:VkValidationCacheEXT to use when validating the
|
|
slink:VkShaderModule.
|
|
|
|
=== New Object Types
|
|
|
|
* slink:VkValidationCacheEXT
|
|
|
|
=== New Enum Constants
|
|
|
|
* Extending elink:VkStructureType:
|
|
** ename:VK_STRUCTURE_TYPE_VALIDATION_CACHE_CREATE_INFO_EXT
|
|
** ename:VK_STRUCTURE_TYPE_SHADER_MODULE_VALIDATION_CACHE_CREATE_INFO_EXT
|
|
|
|
=== New Enums
|
|
|
|
* elink:VkValidationCacheHeaderVersionEXT
|
|
* elink:VkValidationCacheCreateFlagsEXT
|
|
|
|
=== New Structures
|
|
|
|
* slink:VkValidationCacheCreateInfoEXT
|
|
* slink:VkShaderModuleValidationCacheCreateInfoEXT
|
|
|
|
=== New Functions
|
|
|
|
* flink:vkCreateValidationCacheEXT
|
|
* flink:vkDestroyValidationCacheEXT
|
|
* flink:vkMergeValidationCachesEXT
|
|
* flink:vkGetValidationCacheDataEXT
|
|
|
|
=== Issues
|
|
|
|
None.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2017-08-29 (Cort Stratton)
|
|
- Initial draft
|