RFR(XS): 8132525: java -client -XX:+TieredCompilation -XX:CICompilerCount=1 -version asserts since 8130858 (original) (raw)
Roland Westrelin roland.westrelin at oracle.com
Wed Jul 29 18:48:44 UTC 2015
- Previous message: RFR(XS): 8132525: java -client -XX:+TieredCompilation -XX:CICompilerCount=1 -version asserts since 8130858
- Next message: RFR(XS): 8132525: java -client -XX:+TieredCompilation -XX:CICompilerCount=1 -version asserts since 8130858
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Gerard,
Thanks for looking at this.
You put + // With a client VM, -XX:+TieredCompilation causes TieredCompilation + // to be true here (the option is validated later) and + // minnumberofcompilerthreads to exceed CICOMPILERCOUNT. + minnumberofcompilerthreads = MIN2(minnumberofcompilerthreads, CICOMPILERCOUNT); into src/share/vm/runtime/commandLineFlagConstraintsCompiler.cpp file, but that's a constraint function - there should not be any code that sets anything there. Is there somewhere else we can put this code instead of the constraint function?
min_number_of_compiler_threads is a local variable so it shouldn’t be a problem, right?
Roland.
cheers On 07/29/2015 05:51 AM, Roland Westrelin wrote: http://cr.openjdk.java.net/~roland/8132525/webrev.00/
My recent change to the validation of CICompilerCount triggers and assert failure: with -client -XX:+TieredCompilation, TieredCompilation is true when the CICompilerCount option is validated and an erroneous value is used for the min number of threads. TieredCompilation is forced off later in the command line validation process. Roland.
- Previous message: RFR(XS): 8132525: java -client -XX:+TieredCompilation -XX:CICompilerCount=1 -version asserts since 8130858
- Next message: RFR(XS): 8132525: java -client -XX:+TieredCompilation -XX:CICompilerCount=1 -version asserts since 8130858
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the hotspot-compiler-dev mailing list