diff options
| author | Shahbaz Youssefi <syoussefi@chromium.org> | 2024-05-10 00:15:31 -0400 |
|---|---|---|
| committer | Angle LUCI CQ <angle-scoped@luci-project-accounts.iam.gserviceaccount.com> | 2024-05-10 18:43:25 +0000 |
| commit | d1bb6ed8399dd12e79484f30f9e9ded95c25625a (patch) | |
| tree | bf7c4ea2e03902fb12b020f8e2948fc4fbf816c0 /src/tests/deqp_support/deqp_khr_gles3_test_expectations.txt | |
| parent | 8d23fa3f92ed6a40ee1950aea9e0f300caeebe31 (diff) | |
| download | angle-d1bb6ed8399dd12e79484f30f9e9ded95c25625a.tar.gz | |
Document thread-unsafe iterator access to resource maps
By using a proxy type, everywhere resource maps are iterated are clearly
marked as not being thread safe. In most cases, only destruction and
capture/replay iterate over these maps, which means thread safety is not
an issue (or is externally enforced).
The only case where iterators are used in the presence of other contexts
is with ANGLE_request_extension, which is changed to explicitly require
the application to ensure thread safety. In practice, the user is
Chrome which already guarantees this.
Bug: angleproject:8667
Change-Id: I7af13c6433b6955d9c36f9088b3aa4c065e1cfc1
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/5526428
Reviewed-by: Charlie Lao <cclao@google.com>
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Diffstat (limited to 'src/tests/deqp_support/deqp_khr_gles3_test_expectations.txt')
0 files changed, 0 insertions, 0 deletions