[wasm] Do not cache {should_log_code} in compilation state
The compilation state is isolate-independent, so it should not cache the isolate-specific {should_log_code} flag. Instead, we log via the WasmEngine every time. If this turns out to be too expensive, we should introduce an atomic flag in the WasmEngine. R=mstarzinger@chromium.org Bug: v8:8050 Change-Id: I913ada4f86af4c6fa9cd9c5adc8d4e250f6eb7f1 Reviewed-on: https://chromium-review.googlesource.com/c/1451820Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#59335}
Showing
Please
register
or
sign in
to comment