Open
Bug 1483871
Opened 6 years ago
Updated 1 year ago
Consider adding an optimized JIT entry for Function.prototype.call/apply
Categories
(Core :: JavaScript Engine, enhancement, P3)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: jandem, Unassigned)
References
Details
A bit like bug 1483869: I think we could add an "optimized JIT entry" (a feature added for Wasm natives) to the fun_call/fun_apply JSNatives. This JIT entry point would just be a trampoline where we call the target function if it's scripted, or call into C++ if it's not. Once we have that, we can remove the Baseline ICs for call/apply and the similar Ion call optimizations.
Updated•6 years ago
|
Priority: -- → P3
Comment 1•6 years ago
|
||
If we go this route can we please wrap the pointers in a new data structure and make this a little more explicit? There is already enough hidden complexity with these "optimized JIT entries" having surprising coupling to the GC relocation mechanism.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•