You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0a2b068
Browse filesBrowse the repository at this point in the historyBrowse files
https://bugs.webkit.org/show_bug.cgi?id=297699
rdar://158813183
Reviewed by Yijia Huang.
IPInt is acting as a part of validation of wasm. So regardless of
whether IPInt is disabled, we are already compiling IPInt metadata.
This is necessary since BBQ will rely on IPInt metadata. We will enable
IPInt initialization etc. regardless of IPInt is used. When useWasmIPInt
is false, then we immediately tier up to BBQ. But still we should
compile and have IPInt metadata and IPInt callee. This will also remove
WasmToWasm call's callee patchpoints in BBQ and OMG since we will always
emit IPIntCallee pointers and callee will store their own pointer to the
stack slot.
* Source/JavaScriptCore/llint/LLIntData.cpp:
(JSC::LLInt::initialize):
* Source/JavaScriptCore/wasm/WasmBBQJIT.cpp:
(JSC::Wasm::BBQJITImpl::BBQJIT::makeStackMap):
* Source/JavaScriptCore/wasm/WasmOMGIRGenerator.cpp:
(JSC::Wasm::OMGIRGenerator::addLoop):
* Source/JavaScriptCore/wasm/WasmOMGIRGenerator32_64.cpp:
(JSC::Wasm::OMGIRGenerator::addLoop):
* Source/JavaScriptCore/wasm/WasmOMGPlan.cpp:
(JSC::Wasm::OMGPlan::work):
* Source/JavaScriptCore/wasm/js/JSWebAssemblyInstance.cpp:
(JSC::JSWebAssemblyInstance::finalizeCreation):
Canonical link: https://commits.webkit.org/298990@main
0 commit comments