| Age | Commit message (Collapse) | Author |
|
|
|
|
|
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
|
|
|
|
compile
|
|
|
|
- Update known-good
- Generate source
|
|
Change-Id: I650958a8b2607eb3402eb6531909881d4a2ccc0f
|
|
If the implementation reports that it supports this feature, it should
fill out VkFormatProperties3KHR properly.
|
|
|
|
- Update known-good
- Generate source
|
|
During tests, it's hard to determine if the --validation option is
actually working properly. So add an option (--force_errors) to
intentionally force a few validation error messages to make sure
that validation is working properly.
|
|
Expand the scope of the type to allow non trivial types. This helped make the implementation of
parsing command line arguments much cleaner.
|
|
There were a few edge cases which weren't well handled. Examples include
providing a filename and using the vkconfig_output but would ignore the file
name; the filename not being picked up for none file outputs like json and
text. Ammended the wait_for_console_destroy() to only run when not printing
to a file.
|
|
Make sure the following argument is a filename and not another argument.
Also:
Add `--text` as it makes sense to have it as an explicit flag even if it
is the default.
Move --summary to the top, since its the most useful thing to know at a
glance.
|
|
Use `-o <filename>` or `--output <filename>` to specify the filename of which
vulkaninfo will write to in the current directory.
|
|
The main funciton was a chonky 300+ lines of code, this commit pulls out some
of the sections into their own functions to make it easier to read. It also
simplifies the logic in many places by doing so.
|
|
Many of the macro guards in vulkaninfo are unecessary due to not directly
touching the contents of the surfaces outside of already guarded functions.
Thus, there is little point in having guards for stuff that is always able
to compile.
|
|
|
|
The only reason there were global booleans to decide which output to use was due to the macro
WAIT_FOR_CONSOLE_DESTROY. This commit restructures how the win32 function loading operates so
that such globals are no longer necessary. It introduces an OutputCategory enum to declare which
output format to use.
|
|
- Update known-good
- Generate source
|
|
|
|
Updated MoltenVK to 1.1.6 release
|
|
This field has caused numerous crashes and has generally been more trouble than
its worth to have as a default output. Now, a new command line argument is
needed to get vulkaninfo to print tooling info.
|
|
Add a debug callback to vkCreateInstance to debug instance failures,
since there are occassionally errors introduced
which yield validation messages that are currently being missed.
|
|
- 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
|
|
Pipeline stage flags should be set before assigned to pWaitDstStageMask
in VkSubmitInfo.
|
|
- Update known-good
- Generate source
|
|
Previously whenever a SDK was being built, it would have to manually find and
replace the vulkaninfo.rc file with the appropriate values. This commit makes
it simpler by providing a CMake build argument which allows setting the version
to use from the command line.
|
|
- 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
|
|
Change-Id: I1ef9815548f7483ddc712c76210cf938e70c3eae
|
|
When Vulkan-Tools split off from Vulkan-LoaderAndValidationLayers it
inherited the android build scripts, most of which are not relevant to
the projects left in this repo. Also update BUILD.md with latest android
toolchain and remove references to the validation layers.
Change-Id: If982829fc20e14156c52a8f364ef7294733f62cd
|
|
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
|
|
Avoid an amusing and slightly misleading error message:
"The selected gpu (0) is not a valid GPU index. The available GPUs are
in the range of 0 to 18446744073709551615."
|
|
|
|
Expect and deny negative window dimensions.
|
|
- Update known-good
- Generate source
|
|
- Update known-good
- Generate source (no change)
|