2 ms·
The argument that JIT having more information and therefore should/could be able to produce better code never really materialized in most the of mainline JITs
by mike_hearn 10y ago
The argument that JIT having more information and therefore should/could be able to produce better code never really materialized in most the of mainline JITs
Disabling JIT PGO in HotSpot loses you 15-20% performance, so I think it did materialise.
Because Jitting happens at runtime, most jit shy away from complex compiler transformations
I wonder what you classify as complex? Escape analysis driven scalar replacement, PICs, superword optimisations, lock elimination, automatic hardware transactional memory usage all seem very complex to me. HotSpot uses two JITs to trade off speed vs complexity, C1 does a very fast compile with only fast optimisations, C2 will revisit very hot methods and do the extensive optimisation of them.