-
Clemens Backes authored
Adding code can happen in parallel (it includes copying the code to the code region and relocation it). Publishing happens under one lock per native module though. We eventually want to avoid blocking on this lock for too long. This CL prepares that by splitting the actions of adding and publishing code. R=ahaas@chromium.org Bug: v8:10330, v8:10387 Change-Id: Iddbdadfe32e691bbf5e7b387ea947579bc3376f3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2134372 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#66979}
e8ff83dd
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
benchmarks | ||
cctest | ||
common | ||
debugger | ||
debugging | ||
fuzzer | ||
inspector | ||
intl | ||
js-perf-test | ||
memory | ||
message | ||
mjsunit | ||
mkgrokdump | ||
mozilla | ||
test262 | ||
torque | ||
unittests | ||
wasm-api-tests | ||
wasm-js | ||
wasm-spec-tests | ||
webkit | ||
BUILD.gn | ||
OWNERS |