Re:Replacing JavaScript Hot Path with WebAssembly
by RivieraKid on Thursday February 14, 2019 @07:41PM
(#19167545)
> My guess is that the JS implementation of the worst-performing browser is having trouble with the non-1 for-loop steps.
Why would non-1 for loop be slower in some browsers? Does the compiler add some sort of prefetch instruction in the faster browsers based on the loop increment?
Why would non-1 for loop be slower in some browsers? Does the compiler add some sort of prefetch instruction in the faster browsers based on the loop increment?