d29b01737a
This is an analogue of `WTF::AtomicWriteMemcpy` and it should be used for copying data into buffers owned by `SharedArrayBuffer`. While the copy is being done, JS and WASM code can access the `dst` buffer on a different thread. The data observed by JS may not be consistent from application point of view (which is always the case with `SharedArrayBuffer`), but it won't trigger C++ UB and won't upset TSAN. Reads from the `src` buffer are not atomic and should be `src` access should be synchronized via other means. Bug: 340606792 Change-Id: I95fd92d344dce4d463fa281b68b266bb0a8053a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6065639 Reviewed-by: Shu-yu Guo <syg@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Gabriel Charette <gab@chromium.org> Commit-Queue: Eugene Zemtsov <eugene@chromium.org> Cr-Commit-Position: refs/heads/main@{#1398823}
Chromium
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead,
follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.