VkPipelineCache: Do not publically expose internal mutexes
They make it unnecessarily easy to write code that violates the mutex lock requirements.
Replace with the `getOrCreate` pattern already used in vk::Device, which keeps the locking internal.
This change fixes a couple of places that we were accesssing data without correct locking (real bugs).
Bug: b/153194656
Change-Id: I132c450594f4042160b575197789bca7f1a5e25f
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/43650
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by:
Ben Clayton <bclayton@google.com>
Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
Showing
Please
register
or
sign in
to comment