Is there any reason why ION marks the below first function to not_compile,
while it's not a problem for the second ?
1 - function x() { var arr = []; arr[0] = 1; ...some_other_things... }
2 - function x() { var arr = new Array(); arr[0] = 1; .......... }
'array(opcode 190) is not typed?'
Same applies to global methods: 'parseInt' vs 'global.parseInt' (optimizes the
second)
The current 'op-code' interpreter implementation is 'switch-case'. Most
compilers will be converting that into a binary tree (which is fast enough, but
the worst case is ~8 (~300 op codes)).
Although it's a big change, is there any plan for updating that part to a jump
table ? I didn't track yet but would you expect a significant performance gain
from there.
_______________________________________________
dev-tech-js-engine-internals mailing list
dev-tech-js-engine-internals@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
