Unbreak some synchronization edge cases
- Renderer fence signaling only really worked for work in the same
submission. If the fence was submitted standalone later, there would
be no renderer work tagged with this fence, and so no ordering.
- Get rid of old uncounted fence operations. This is a landmine.
Bug: b/132897411
Test: dEQP-VK.api.copy_and_blit.*
Test: dEQP-VK.binding_model.*
Test: dEQP-VK.query_pool.*
Test: dEQP-VK.api.object_management.*
Test: dEQP-VK.memory.pipeline*
Change-Id: I9050b96d111a6c348c5675724c8017c483c06182
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/31188Reviewed-by:
Alexis Hétu <sugoi@google.com>
Tested-by:
Chris Forbes <chrisforbes@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Showing
Please
register
or
sign in
to comment