Commit 7390c2fc authored by Mircea Trofin's avatar Mircea Trofin Committed by Commit Bot

[wasm] Use the C_WASM_ENTRY code type for cctest GetWrapperCode()

It appears in the cctest context, both the old STUB, and the current 
WASM_FUNCTION "just work"; however, in the upcoming off-the-gc wasm 
world, we codegen call sites differently on x64 - far calls for 
js-to-wasm (this case), and near calls otherwise.

Bug: 
Change-Id: Iebf8acf164f07742fc367b7bbf266913dbc60c46
Reviewed-on: https://chromium-review.googlesource.com/735131Reviewed-by: 's avatarBen Titzer <titzer@chromium.org>
Commit-Queue: Mircea Trofin <mtrofin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#48889}
parent 4d177e78
...@@ -353,7 +353,7 @@ Handle<Code> WasmFunctionWrapper::GetWrapperCode() { ...@@ -353,7 +353,7 @@ Handle<Code> WasmFunctionWrapper::GetWrapperCode() {
} }
CompilationInfo info(ArrayVector("testing"), isolate, graph()->zone(), CompilationInfo info(ArrayVector("testing"), isolate, graph()->zone(),
Code::WASM_FUNCTION); Code::C_WASM_ENTRY);
code_ = compiler::Pipeline::GenerateCodeForTesting(&info, descriptor, code_ = compiler::Pipeline::GenerateCodeForTesting(&info, descriptor,
graph(), nullptr); graph(), nullptr);
CHECK(!code_.is_null()); CHECK(!code_.is_null());
......
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