Skip to content

Conversation

@MathiasMagnus
Copy link
Contributor

@MathiasMagnus MathiasMagnus commented Dec 6, 2024

artem-lunarg and others added 30 commits October 9, 2024 18:02
There are more places to do this but that's a minimal change for the
current task
This creates a buffer bound to the host visible coherent memory type.
All implementations should support this according to the specification.
This needs shader instrumentation support - similar to descriptors
This test should trigger an error during QueueSubmit when the issue
is fixed.
They are never used through their base class,
so might as well remove the added complexity
Without going through an intricate dance with git to change the remote
URL of a repository, it's simplest to just nuke the cloned folder, as
we have to do a clean clone anyway.
The documentation states that users can override where to take a
dependency from via variables like VULKAN_HEADERS_INSTALL_DIR, however
the helper.cmake written by the scripts/CMakeLists.txt FORCE updates
the cache variable to the location inside known_good.json, practically
overwriting the user-provided path given on the CLI using -D, also
going into the cache.
spencer-lunarg and others added 23 commits November 18, 2024 12:56
This removes ValidatorState ownership transfer helper.
It was mostly additional abstraction layer that copied local variables
and the result was stored as another local variable.

Also replaced VUID-vkQueueSubmit-pSubmits-04626 with unassigned VUID
when resource is EXCLUSIVE. 04626 is only about checking CONCURRENT
resource properties. It also checks resource itself but not a barrier
properties which is needed in unassigned VUID.
Remove the need for a staging std::vector
Previously, there were top level ValidationObjects stored in
layer_data_map. These didn't do validation but contained more
ValidationObjects in the object_dispatch vector (and a few others).

This caused much confusion, since some members were only used
at the top level and others only at the lower level.  When uses
got mixed up, this could only be detected at runtime since the
members were always available even though they might not be set
up correctly.

Start to split this up by moving top level functionality to
a new DispatchObject class. This does handle wrapping and coordination
of validation by the child ValidationObjects. There are still many
members related to settings, extension status, logging  and dispatch
tables that are duplicated at both levels. Fixing this is a big
change that needs to be done separately.

Also note that DispatchObject and ValidationObject are still used
to represent both VkDevice and VkInstance. This will require much
more work to undo.
While browsing/modifying this JSON file I spotted a glaring typo in the
main layer description, and ended up fixing a few more in the settings
descriptions down below.
@CLAassistant
Copy link

CLAassistant commented Dec 6, 2024

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 3 committers have signed the CLA.

✅ MathiasMagnus
❌ Eearslya
❌ MarijnS95
You have signed the CLA already but the status is still pending? Let us recheck it.

@MathiasMagnus MathiasMagnus force-pushed the downstream-1.3.302 branch 2 times, most recently from 6966d4b to 16be034 Compare December 6, 2024 15:15
@aqnuep aqnuep merged commit cce243b into sc_main Dec 9, 2024
20 of 21 checks passed
@aqnuep aqnuep deleted the downstream-1.3.302 branch December 9, 2024 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.