tree 2e0f7452bd19881895b2c9220a3c4902958267d3
parent ad675fa1d6617ff7fe5965845152ba71f33caf61
author Nicolas Capens <capn@google.com> 1492528477 -0400
committer Nicolas Capens <capn@google.com> 1492615828 +0000

Fix potential data race in mutex lock implementation.

Writing or reading an ordinary volatile boolean does not provide memory
ordering guarantees. Use atomic<bool> with release and acquire semantics
instead. On x86 this should have no impact on the generated code, since
it architecturally offers strong memory ordering guarantees.

Bug chromium:710753

Change-Id: I5aa2a6eeecfcd691a0aa8d06fd067f9d59ab13c3
Reviewed-on: https://swiftshader-review.googlesource.com/9328
Reviewed-by: Corentin Wallez <cwallez@google.com>
Reviewed-by: Nicolas Capens <capn@google.com>
Tested-by: Nicolas Capens <capn@google.com>