| Age | Commit message (Collapse) | Author |
|
- Update known-good
- Generate source
|
|
- Update known-good
- Generate source
|
|
Updated MoltenVK to 1.1.8
|
|
- Update known-good
- Generate source
|
|
- Update known-good
- Generate source
|
|
|
|
|
|
|
|
|
|
|
|
|
|
VkPhysicalDeviceIDProperties can come from 1.1 but also from support for
multiple extensions. This makes the autogen properly check that one of the
required extensions is supported.
|
|
Some of the pNext chains didn't make use of the generic chain printers. Since they aren't
being used in code, it is good to disable the generation of those printers.
|
|
Only generate the early exit if there doesn't exist an bitmask which has a
value of 0. For example, VK_RESOLVE_MODE_NONE has a value of 0, but it would
never be printed without this special case.
|
|
Replace numeric values with the textual version, this makes it easier to read
the code and verify that it is correct.
|
|
This makes unknown flags put the value of the flag bits in the returned string
so that if an error does occur, users can see which value(s) were returned.
|
|
Previously the version used was up to the caller of the chain printer function
to provide, but this was unnecessary as the printer should always use the
version of the type (instance or gpu) of printer in question. If both are
specified, it uses the gpu version since that implies physical_device functions.
|
|
Previously if a key-value pair wanted to be printed with padding, so the
output would be aligned, it would have to pass in the width into each and
every printer statement. This commit makes the min_key_width value set
per object (in the object_stack) so it can be set after the object is started
and re-used over and over. This simplifies the code gen and useability of
the Printer class.
|
|
Make the autogen and vulkaninfo source code support printing of the pNext chain
in VkQueueProperties2KHR. Several structs were added to this chain recently and
are helpful information to be printed. This required special casing the output
so that it only prints the elements that are 'valid' and modifying the chain
printer to unset the next header flag.
|
|
Generate a structure that contains all the structures in the pNext chain as
members rather than relying on malloc to allocate memory for them.
|
|
The 1.3 update forgot to rename
VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SHADER_INTEGER_DOT_PRODUCT_FEATURES_KHR to
VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SHADER_INTEGER_DOT_PRODUCT_FEATURES as this
is the non-aliased name. Without it, the fix wouldn't be applied.
|
|
|
|
|
|
|
|
Only changes are making the autogen print all required structs, and
moving from using the EXT version of tool properties to the core version.
|
|
- Update known-good
- Generate source
|
|
- Update known-good
- Generate source
|
|
If the implementation reports that it supports this feature, it should
fill out VkFormatProperties3KHR properly.
|
|
- Update known-good
- Generate source
|
|
- Update known-good
- Generate source
|
|
|
|
Updated MoltenVK to 1.1.6 release
|
|
- Update known-good
- Generate source
|
|
The structure VkPhysicalDeviceShaderIntegerDotProdcutFeaturesKHR contains only a single
feature boolean flag. However, before the final version was published to the public, it
had many boolean flag values. Pre-release drivers often contain support for unpublished
extensions, such as VK_KHR_shader_integer_dot_product. Because the final version was
much smaller than the pre-release version, several drivers try to write to members that
do not exist in the final version, which cause out of bounds writes to the features struct
that vulkaninfo passes into the driver.
By increasing the size of the features struct allocation manually, we can prevent potential
crashes from OOBs writes from drivers.
|
|
- Update known-good
- Generate source (no change)
|
|
- Update known-good
- Generate source
|
|
- Update known-good
- Generate source
|
|
- Update known-good
- Generate source
|
|
- Update known-good
- Generate source
|
|
Currently some of the generators use a fixed child index to locate
extension enums, which will break if comment blocks are added near the
top of an extension definition. This change makes the enum lookup more
robust by searching for the expected enum name instead of using a
hard-coded offset.
|
|
Bring forward the update_deps script in this repo to match VVL
|
|
f-strings are a python feature which allow more natural formatting of text, making
the code easier to read and work with.
|
|
64 bit flags use the bitvalues field instead of the requires field in the XML
to specify the flagbits name. Thus the autogen needed to account for that.
In addition, if a flag was promoted to core, the autogen didn't use the core
version, this commit also fixes that.
|
|
- Update known-good
- Generate source
|
|
- Update known-good
- Generate source
|
|
When the working group changes the name of a constant:
VK_KHR_MAINTENANCE1_SPEC_VERSION ->
VK_KHR_MAINTENANCE_1_SPEC_VERSION
they will still #define the original name to maintain backward
compatibility with existing code that uses it:
#define VK_KHR_MAINTENANCE_1_SPEC_VERSION 2
#define VK_KHR_MAINTENANCE_1_EXTENSION_NAME "VK_KHR_maintenance1"
#define VK_KHR_MAINTENANCE1_SPEC_VERSION VK_KHR_MAINTENANCE_1_SPEC_VERSION
#define VK_KHR_MAINTENANCE1_EXTENSION_NAME VK_KHR_MAINTENANCE_1_EXTENSION_NAME
In this case, we need to ignore the non-numeric _SPEC_VERSION and
unquoted _EXTENSION_NAME constants because they don't define a separate
extension.
|
|
- Update known-good
- Generate source
|
|
|
|
- Update known-good
- Generate source
|
|
- Update known-good
- Generate source (no change)
|