RFR(S): 8154151: VM crashes with assert "Ensure we don't compile before compilebroker init"
nils.eliasson at oracle.com
Thu Apr 14 13:17:47 UTC 2016
Please review this fix.
In JDK-8150646 I added an assert in compile_method that the compiler
must not be NULL. Before there was a return there that just ignored the
Running the VM with the flag combination -Xcomp and
-XX:TieredStopAtLevel=0 creates a special situation: UseInterpreter is
set to false (but the interpreter it is still available) and then some
essential methods are forced to be compiled, but the initial complevel
becomes 0 and hits the assert in compileBroker.
We could discuss if it should be allowed to submit compiles on level 0,
a change that would become a bit larger. This time I choose to extend
the _initalized check in compile_method. I didn't add any logging or
warning because this is really a corner case.
(Ignore the extra tags in the webrev)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-compiler-dev