-
Notifications
You must be signed in to change notification settings - Fork 477
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Change log for February 16, 2023 Vulkan 1.3.241 spec update:
Github Issues: * Clarify apiext:VK_EXT_debug_utils object support (public issue 1668, public pull request 2034). * Fix capitalization typos in a few VUs (public pull request 2050). * Parameterize asciidoc includes of asciidoc files from `vkspec.adoc` using `{chapters}` attribute (public pull request 2051). Internal XML Schema Issues: Several needed XML schema changes are introduced in this update which may impact downstream XML users who are doing their own parsing. Users of our Python generator framework are unlikely to be impacted. If you have difficulty adapting to these changes, please open an issue on the Vulkan-Docs Github repository. * Introduce a new `depends` attribute to the XML schema, replacing the `requires` and `requiresCore` attributes of `<extension>` tags, and the `features` and `extension` attributes of `<require>` tags. This is an intentional and unavoidable breaking change, allowing us to correctly express more complex dependencies. XML users doing their own XML parsing and needing this information must treat the `depends` attribute as a boolean expression. This change also adds a description of the different interpretation of device and instance extension dependencies in a single place in the new <<extensions, "`Extension Dependencies`">> section at the start of the extensions appendix, rather than including a boilerplate comment about "`device-level extensions`" with each relevant extension dependency described later in the appendix (internal issue 2883). * Import XML, script, and config file changes from the Vulkan SC spec repository. This change uses the `api` XML attribute to specialize some tags for the Vulkan and Vulkan SC APIs. While this is not a new attribute, it has not been extensively used in this fashion previously in this repository. XML users doing their own XML parsing must now filter out tags with `api` attributes not matching the API they are generating, and must also filter out `<extension>` tags whose `supported` attribute does not include that API (internal issue 3348). * Remove some redundancies from refactored XML dependencies (internal merge request 5713). * Express correct XML dependencies of apiext:VK_KHR_buffer_device_address, now that the new `depends` schema supports that (internal merge request 5721). * Add a new `deprecated` attribute to several tags in XML schema which provides some guidance as to why an API was deprecated. Remove `comment` text which some downstream XML parsers were using to infer deprecation, which was never an intended or supported purpose of the comments (public ash-rs/ash issue 670, internal merge request 5537). Other Internal Issues * Expand the definition of <<fundamentals-validusage-enums, "`valid enumerant value`">> to include whether the extension or core version defining that enumerant is enabled or supported. This has a global effect on corresponding VU statements, and the Vulkan Validation Layer is being updated accordingly (internal issue 2912). * Update the <<synchronization>> chapter in several places to clarify that pipeline barriers work only within a single queue (internal issue 3365). * Add ename:VK_PIPELINE_STAGE_2_ACCELERATION_STRUCTURE_COPY_BIT_KHR in a few places it was missing, and update description for copy commands to specify where it should be used with apiextVK_KHR_synchronization2 rather than ename:VK_PIPELINE_STAGE_2_ACCELERATION_STRUCTURE_BUILD_BIT_KHR (internal merge request 5604). * Fix typos in `proposals/VK_KHR_video_decode_queue.adoc` (internal merge request 5646). * Add dynamic state to apiext:VK_EXT_discard_rectangles (ename:VK_DYNAMIC_STATE_DISCARD_RECTANGLE_ENABLE_EXT and ename:VK_DYNAMIC_STATE_DISCARD_RECTANGLE_MODE_EXT) and for apiext:VK_NV_scissor_exclusive (ename:VK_DYNAMIC_STATE_EXCLUSIVE_SCISSOR_ENABLE_NV) that was overlooked in apiext:VK_EXT_extended_dynamic_state3. While this is adding functionality to existing extensions, the implementers of these extensions have all signed off on this change (internal merge request 5671). * Disallow ename:VK_DESCRIPTOR_TYPE_INLINE_UNIFORM_BLOCK in slink:VkDescriptorGetInfoEXT VU 08018 (internal merge request 5681). * Rearrange some language in flink:vkGetRayTracingShaderGroupHandlesKHR and flink:vkGetRayTracingCaptureReplayShaderGroupHandlesKHR to follow the style guide (internal merge request 5683). * Update to new Docker image SHA for CI and building specs (internal merge request 5688). * Add `SPV_EXT_fragment_fully_covered` to XML `<spirvextensions>` section (internal merge request 5689). * Add missing pname:pNext description to slink:VkVideoDecodeH264DpbSlotInfoKHR (internal merge request 5701). * Add missing internal links for the term <<pipelines-graphics-subsets-fragment-shader, fragment shader state>> (internal merge request 5704). * Move ename:VK_DYNAMIC_STATE_PRIMITIVE_TOPOLOGY VU common draw vertex binding VUs, and word VUs 03420 and 07500 the same, minus the reference to pname:dynamicPrimitiveTopologyUnrestricted (internal merge request 5708). * Ban some advanced blend modes from slink:VkColorBlendEquationEXT that must be set using a different mechanism (internal merge request 5705). * Update copyright dates to 2023, and add CI check for Khronos-copyright files (internal merge request 5716). * Add clarifying NOTE and typo fixes for apiext:VK_HUAWEI_cluster_culling_shader (internal merge request 5718). * Add missing XML dependencies on apiext:VK_KHR_get_physical_device_properties2 to several extensions (internal merge request 5719). * Remove flink:vkCmdResolveImage VUs where pname:srcImage is of type ename:VK_IMAGE_TYPE_3D (internal vulkansc issue 178). New Extensions: * apiext:VK_EXT_image_sliced_view_of_3d * apiext:VK_ARM_shader_core_properties * apiext:VK_QCOM_multiview_per_view_render_areas
- Loading branch information
Showing
602 changed files
with
6,924 additions
and
1,483 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
// Copyright (c) 2023 Arm Ltd. | ||
// | ||
// SPDX-License-Identifier: CC-BY-4.0 | ||
|
||
include::{generated}/meta/{refprefix}VK_ARM_shader_core_properties.adoc[] | ||
|
||
=== Other Extension Metadata | ||
|
||
*Last Modified Date*:: | ||
2023-02-07 | ||
*IP Status*:: | ||
No known IP claims. | ||
*Contributors*:: | ||
- Jan-Harald Fredriksen, Arm Ltd. | ||
|
||
=== Description | ||
|
||
This extension provides the ability to determine device-specific performance | ||
properties of Arm GPUs. | ||
|
||
It exposes properties for the number of texel, pixel, and fused multiply-add | ||
operations per clock per shader core. | ||
This can be used in combination with the | ||
`apiext:VK_ARM_shader_core_builtins` extension that provides the ability to | ||
query the number of shader cores on the physical device. | ||
|
||
include::{generated}/interfaces/VK_ARM_shader_core_properties.adoc[] | ||
|
||
=== Version History | ||
|
||
* Revision 1, 2023-02-07 (Jan-Harald Fredriksen) | ||
** Initial draft. |
Oops, something went wrong.