News for hackers. Stuff that matters.
Re:Faster JavaScript Calls by thechao on Monday February 15, 2021 @12:41PM (#26144981)
Is it better, or worse, than dumping the adapter object into the stack? Clearly, their numbers show it’s better. Also, runtime variable calling conventions are a nightmare. Telling the callee the calling convention (in some sort of mixed mode) still requires a flag ... like an integer? So, it seems they have to pay the cost of the integer no matter what.

Maybe I’m wrong — could you elaborate how you’d do it?

Re:Faster JavaScript Calls by josefx on Monday February 15, 2021 @04:40PM (#26147818)
> Clearly, their numbers show it’s better.

Their numbers seem cherry picked or is Turbo Fan actually unable to inline code?

Re:Faster JavaScript Calls by ash_gti on Monday February 15, 2021 @06:22PM (#26149002)
TF can inline, but if it runs that optimization then the benchmark would be turned into a constant, so it wouldn't be measuring the call overhead of the way arguments are passed.
Re:Faster JavaScript Calls by josefx on Wednesday February 17, 2021 @04:19AM (#26164397)
Inlining is something I would think also eliminates stack frames. So a comparison between an optimization that gets rid of a complicated stack frame and a compiler that has inlining turned off isn't something I would consider ideal.