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>
diff --git a/src/Vulkan/BUILD.gn b/src/Vulkan/BUILD.gn
index 1bb14a8..a8afc99 100644
--- a/src/Vulkan/BUILD.gn
+++ b/src/Vulkan/BUILD.gn
@@ -57,6 +57,7 @@
defines += [
"SWIFTSHADER_ENABLE_ASTC", # TODO(b/150130101)
"SWIFTSHADER_LEGACY_PRECISION=true", # TODO(chromium:1299047)
+ "SWIFTSHADER_ZERO_INITIALIZE_DEVICE_MEMORY",
]
}
