bd5b3ae542
With shared space (instead of the shared isolate), the AccessorInfo implementation of SharedArray's length property is no longer threadsafe. Until AccessorInfos can be put into shared or RO space, go back to storing the length field as a per-instance in-object field, which is unfrotunately a little wasteful. Bug: v8:12547 Change-Id: I99c1cbf26047da48a4b4c11e14ab7def7d4e4f60 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4039309 Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Auto-Submit: Shu-yu Guo <syg@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#84408} |
||
---|---|---|
.. | ||
client-gc.js | ||
condition-workers.js | ||
condition.js | ||
mutex-workers.js | ||
mutex.js | ||
shared-array-atomics-workers.js | ||
shared-array-atomics.js | ||
shared-array-surface.js | ||
shared-array-workers.js | ||
shared-external-string-dictionary-lookup.js | ||
shared-external-string-megamorphic-ic.js | ||
shared-string-in-code-object.js | ||
shared-string-in-weak-map.js | ||
shared-string-promotion-major.js | ||
shared-string-promotion-minor.js | ||
shared-string.js | ||
shared-struct-atomics-workers.js | ||
shared-struct-atomics.js | ||
shared-struct-property-storage.js | ||
shared-struct-surface.js | ||
shared-struct-workers-optimized-code.js | ||
shared-struct-workers.js | ||
shrink-large-object.js | ||
value-serializer.js |