Commit c624261e authored by Thibaud Michaud's avatar Thibaud Michaud Committed by Commit Bot

[wasm] Access CodeTracer through the wasm engine

Set the wasm engine in the {PipelineData} constructor used for JS to
Wasm wrapper compilation, so that the code tracer can be accessed
independently from the isolate.

R=mvstanton@chromium.org

Bug: chromium:1032677
Change-Id: Id26d1695446251e310fe7dbd9cc7b04f8f1ad175
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1973738Reviewed-by: 's avatarMichael Stanton <mvstanton@chromium.org>
Commit-Queue: Thibaud Michaud <thibaudm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#65595}
parent 26653c94
...@@ -214,6 +214,7 @@ class PipelineData { ...@@ -214,6 +214,7 @@ class PipelineData {
NodeOriginTable* node_origins, JumpOptimizationInfo* jump_opt, NodeOriginTable* node_origins, JumpOptimizationInfo* jump_opt,
const AssemblerOptions& assembler_options) const AssemblerOptions& assembler_options)
: isolate_(isolate), : isolate_(isolate),
wasm_engine_(isolate_->wasm_engine()),
allocator_(allocator), allocator_(allocator),
info_(info), info_(info),
debug_name_(info_->GetDebugName()), debug_name_(info_->GetDebugName()),
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment