dc35435802
Additionally a bug in the wasm-to-C wrapper got fixed, which caused problems with the thread-in-wasm flag: An invalid effect-chain got constructed. With the write of the thread-in-wasm flag not being properly placed in the effect chain, the write got scheduled too late. R=jkummerow@chromium.org Bug: v8:11713 Change-Id: I351bf622081850b7b0c7aebfd798d1e73ae34a4a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2867468 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#74340} |
||
---|---|---|
.. | ||
BUILD.gn | ||
callbacks.cc | ||
DEPS | ||
finalize.cc | ||
globals.cc | ||
hostref.cc | ||
memory.cc | ||
multi-return.cc | ||
reflect.cc | ||
run-all-wasm-api-tests.cc | ||
serialize.cc | ||
startup-errors.cc | ||
table.cc | ||
testcfg.py | ||
threads.cc | ||
traps.cc | ||
wasm-api-test.h | ||
wasm-api-tests.status |