Re:Notes on debugging HotSpot's JIT compilation
by comonoid on Tuesday March 26, 2024 @06:35AM
(#39826162)
Well, inlining is not necessary, good old interprocedure analysis would resolve it too.
[ Parent
| on HN ]
Re:Notes on debugging HotSpot's JIT compilation
by lewurm on Tuesday March 26, 2024 @08:02AM
(#39826795)
Sure, but neither javac (the Java to bytecode compiler) or HotSpot are doing that. The former tries to preserve as much as possible, and for the latter interprocedure analysis is too costly at run-time.
Re:Notes on debugging HotSpot's JIT compilation
by anonymous-panda on Tuesday March 26, 2024 @12:23PM
(#39829666)
Could javac do the analysis and record it in the bytecode for HotSpot to optimize? Or is this kind of hybrid teamwork not done?
Re:Notes on debugging HotSpot's JIT compilation
by mike_hearn on Tuesday March 26, 2024 @12:31PM
(#39829761)
It is done, but for this case the problem is partial compilation. For this you'd need methods to be tagged as pure, but that assumption needs to propagate and it could be violated by a library being upgraded.