Thanks, Lasse.
http://codereview.chromium.org/6814012/diff/1/src/compiler.cc File src/compiler.cc (right): http://codereview.chromium.org/6814012/diff/1/src/compiler.cc#newcode606 src/compiler.cc:606: On 2011/04/08 12:54:18, Lasse Reichstein wrote:
The preparser should be able to detect this and store it in the
preparser data
with the other data that are set for lazy functions. On the other hand, if this is sufficient, I guess it'll do.
Preparser doesn't yet detect strict mode. Once it does (and it will have to for early errors) I'll remove this. http://codereview.chromium.org/6814012/diff/1/test/mjsunit/strict-mode-opt.js File test/mjsunit/strict-mode-opt.js (right): http://codereview.chromium.org/6814012/diff/1/test/mjsunit/strict-mode-opt.js#newcode29 test/mjsunit/strict-mode-opt.js:29: var MAX = 10000000; On 2011/04/08 12:54:18, Lasse Reichstein wrote:
That's a lot. Is it really necessary? Are there any flags you could use to make optimization more frequent
so you
don't need as big a loop?
Turns out we inline even with one zero removed so I am taking one zero out for the landing http://codereview.chromium.org/6814012/ -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
