RFC: Diagnostic flag to crash VM on JIT compilation failure?
vladimir.kozlov at oracle.com
Thu Oct 11 18:14:33 UTC 2018
Okay, in such case I would suggest to make general (not Shenandoah specific) diagnostic flag similar to
AbortVMOnException flag. Something like AbortVMOnCompileFailure.
And code should by in CompileBroker::post_compile().
On 10/11/18 10:44 AM, Aleksey Shipilev wrote:
> On 10/11/2018 07:39 PM, Vladimir Kozlov wrote:
>> Why to crush? Do you want to attach debugger?
> Sorry, I should have been clearer.
> I want to run our performance tests with usual compiler configuration, and make VM fail if/when we
> fail to compile the method for some reason -- probably due to VM bugs -- instead of silently
> regressing performance, and leaving me scratching my head what had happened. This might be of
> interest for high-performance users too, if they want to treat current graceful degradation as error
> condition instead.
> This is similar to CompileTheWorld, except it does normal compilation with usual profiling and
> optimization, basically running in the mode we would expect production to run.
More information about the hotspot-compiler-dev