tree c133030653c5ce8e30fd67753e55a8387b0c09fc
parent 1f456938b36f02404830c2e831e328d8ba8d30cd
author Nicolas Capens <capn@google.com> 1561470484 -0400
committer Nicolas Capens <nicolascapens@google.com> 1561551662 +0000

Don't treat class-memaccess warning as error

Cache keys must be guaranteed to have no uninitialized bits so that they
can be compared with memcmpy() and hash values can be computed from
their raw memory representation. We do this by calling memset(this, ...)
in the Memset<T> class used as the first base class. This is safe since
no other constructor has run yet (similar to doing placement new in
zeroed out memory). GCC 8.2's class-memset warning should thus not be
treated as an error.

Bug: b/135744933
Bug: b/134932616
Change-Id: I378b663281b1737359330c29c8c73934e7dd20f7
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33368
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>