Gavin Barraclough <[email protected]> wrote:
> We were (and remain) reluctant to accept a duplicate of the JIT into
the tree, rather > than a port of the existing JIT utilizing the
MacroAssembler abstraction. We are
> concerned that it would be
extremely difficult to continue to maintain such a port as
> we move the
JIT technology forwards.
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.
Toshi
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
