Umm. IMHO The existing JIT is not well designed, with processor-
specific constants everywhere and "optimizations" such as inlinining
huge blocks of weakly-optimized code instead of making a function
call to properly-optimized code.
These issues make it difficult to both port and maintain.
If the other JIT is better designed than the current one, IMHO it
should be considered for inclusion.
Luckily, performance doesn't have to be a matter of opinion. You can
benchmark it.
I'm having a hard time understanding from your comment what
optimization changes you think are appropriate, but if you can produce
a patch that implements your idea, and shows a benefit on a benchmark,
I'd be happy to review it.
Cheers,
Geoff
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
