op_call_NotJSFunction is only referenced during the final linking phase.
Actual compilation requires two distinct operations: 1) planting the call
instruction and 2) linking the call target after the code has been relocated.
Here is the (64-bit) version of the call + link logic:
...
prese
Grep gives nothing, there is only one mention of op_call_NotJSFunction
in privateCompileCTIMachineTrampolines(JITOpcodes.cpp), but I don't see any
call instruction there.
Still can't understand how calls orgonized in SXF.
On 24 July 2012 20:07, Filip Pizlo wrote:
>
> On Jul 24, 2012, at 5:51 AM
On Jul 24, 2012, at 5:51 AM, vahe vardanyan wrote:
> Hi all.
>
> As I understand in SFX all non JS functions calls go trough
> JITStubs:op_call_NotJSFunction function.
>
> But in which point, where, the op_call_NotJSFunction function is called?
It's called from code generated by the JIT. I w
Hi all.
As I understand in SFX all non JS functions calls go trough
JITStubs:op_call_NotJSFunction function.
But in which point, where, the op_call_NotJSFunction function is called?
Can anyone please explain how function calls are implemented in SFX(simple
jit).
Thanks for attention
___
4 matches
Mail list logo