On Mon, Feb 29, 2016 at 1:23 PM, Jakob Kummerow <[email protected]> wrote: > This is indeed surprising. > Crankshaft predates ES6, so this has nothing to do with ES6 const. That > said, I don't see why this function would bail out; and in a quick repro > attempt it doesn't. Do you have an example I can run that reproduces this > behavior? > > Also, is this actually a performance problem for you? Crankshaft aborts > compilation in some cases by design, often there's no need to worry about > it.
If it helps, see [0] - we had to revert some changes to the url module because of this issue. That's with V8 4.8.271.17. The benchmarks are in [1]. They normally run in a child process but you can run an individual benchmark directly with `./node benchmark/url/url-parse.js type=one n=25e4`. [0] https://github.com/nodejs/node/pull/5300 [1] https://github.com/nodejs/node/blob/v5.7.0/benchmark/url/url-parse.js -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
