Changes between Version 18 and Version 19 of JavaScript performance improvement ideas


Ignore:
Timestamp:
Nov 6, 2007 9:44:31 PM (17 years ago)
Author:
eric@webkit.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JavaScript performance improvement ideas

    v18 v19  
    1919 * Use bytecode or something similar to make the interpreter non-recursive so it doesn't use so much stack. But the inner loop has to be coded carefully because obvious ways of doing will regress performance instead of speeding it up. (direct threading, subroutine threading, context threading)
    2020
    21  * Constant folding. This could be done purely by the parser, for strings, numbers, even regexps.
     21 * Constant folding. This could be done purely by the parser, for strings, numbers, even regexps.  Only a couple tests use constants which could be folded (long strings built with +), however none of those do so in a loop (where we would see much benefit).
    2222
    2323 * Special-case numeric code. If we can prove some values are guaranteed to be numeric, we could evaluate expressions involving them purely using doubles, without converting intermediate values to immediate values or NumberImps at all.