RFR: 8143151: [JVMCI] assertion for allocation of "too many" CompileTasks must take JVMCI into account
igor.ignatyev at oracle.com
Wed Nov 18 19:15:02 UTC 2015
Looks good to me.
> On Nov 18, 2015, at 8:25 PM, Christian Thalinger <christian.thalinger at oracle.com> wrote:
> Makes sense. Looks good.
>> On Nov 17, 2015, at 12:07 PM, Doug Simon <doug.simon at oracle.com> wrote:
>> Normally -Xcomp implies blocking compilation (i.e., -Xbatch). However when a JVMCI compiler is in use, the CompileBroker has special logic to prevent blocking compilations from causing a deadlock between JVMCI compiler threads and other threads. Until they are themselves compiled, JVMCI compilers are slower than native compilers. This means the compilation queue can back up quickly and require more CompileTasks to be created. There's an assertion that the number of CompileTasks allocated never exceeds 10000. This assertion needs to be modified if a JVMCI compiler is in use.
More information about the hotspot-compiler-dev