tree 08caa32b1c3a4bb94ebb568956d213fa6d662f9c
parent b7b7cb76042a6374b038f1d18f4863d714960bb0
author Nicolas Capens <capn@google.com> 1633038500 -0400
committer swiftshader-scoped@luci-project-accounts.iam.gserviceaccount.com <swiftshader-scoped@luci-project-accounts.iam.gserviceaccount.com> 1633066636 +0000

Restore zero-initialization of memory allocations

This change replaces the single sw::allocate() with three variants that
make it explicit whether or not the memory is initialized. For now, only
sw::allocateZero() is used, to work around MemorySantizer errors that
have been encountered.

Subsequent changes will split vk::allocate() too, to discern between the
different kinds of allocations made at the Vulkan level. These will then
systematically call sw::allocateZeroOrPoison() to isolate the culprit of
MemorySanitizer errors. Eventually they should use
sw::allocateUninitialized() to improve performance.

Bug: b/140991626
Change-Id: I962c91edab474b8791b1e2acb999c7e7e9718a5e
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/57728
Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Commit-Queue: Nicolas Capens <nicolascapens@google.com>