tree d3ffbee1871ca7f30daa7a78f44e7e3c9351cc01
parent c167893a11ab6dad9faa23e14e4690a99b804225
author Nicolas Capens <capn@google.com> 1653512646 -0400
committer Nicolas Capens <nicolascapens@google.com> 1653585584 +0000

Only zero-initialize device memory for non-MSan GN builds

Chromium might still be susceptible to information disclosure issues if
we don't clear Vulkan "device" memory allocations, so we keep the
previous behavior of zeroing the memory except for MSan builds through
the SWIFTSHADER_ZERO_INITIALIZE_DEVICE_MEMORY flag.

All other builds now leave the memory uninitialized.

sw::allocateUninitialized() was renamed to sw::allocate().

Bug: b/140991626
Change-Id: I05275fca454481107b75fffbca1d37afd757937d
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/66009
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>