smaug wrote:
With (2) it becomes hard to beat v8.
Neutralizing V8 is probably both sufficient to compete, and the best we
can do with our hackers on hand to work on such projects. Winning at
regexp perf or breaking some speed-of-sound barrier not yet breached by
any engine does not seem like a priority, although it would be
interesting research. (E.g., using SIMD instructions for regex
execution, something Intel has researched.)
Also, if (2) requires significant work to make it integrate well with
SM, doesn't
it pretty much become (3). (Though, I'm not a SpiderMonkey hacker)
This is a key point. V8 is more intertwingled than JSC. Pulling on the
yarn may pull big tangles out of the big ball.
But anyhow, I agree something needs to be done. regexp slowness shows
up in too many profiles these days.
What about contacting Apple principals who maintain JSC and checking
whether they want to fix YARR? Just because their bug has been idle for
years does not mean we should assume they aren't thinking of, planning,
or even about to start working on JITting all the regexps.
/be
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
