RFR: 8166125: [JVMCI] Missing JVMCI flag default values

Christian Thalinger cthalinger at twitter.com
Thu Sep 15 18:40:35 UTC 2016


Crazy :-)  Well, better late than never.  Looks good.

> On Sep 15, 2016, at 8:38 AM, Doug Simon <doug.simon at oracle.com> wrote:
> 
> David noticed this while investigating some performance regressions that occurred around the time we switched from a separate JVMCI VM binary (i.e. COMPILERJVMCI) to -XX:+UseJVMCICompiler.
> 
> -Doug
> 
>> On 15 Sep 2016, at 20:34, Christian Thalinger <cthalinger at twitter.com> wrote:
>> 
>> Nobody noticed until now?
>> 
>>> On Sep 15, 2016, at 4:10 AM, David Leopoldseder <david.d.leopoldseder at oracle.com> wrote:
>>> 
>>> Hi,
>>> 
>>> Please review this patch.
>>> 
>>> Bug: 
>>>    During the initial commit for the JVMCI JEP some options JVMCI sets differently than c2 have been forgotten.
>>> Fix:
>>>    Set the options if INCLUDE_JVMCI is true and -XX:+UseJVMCICompiler.
>>> 
>>> http://cr.openjdk.java.net/~davleopo/JDK-8166125/webrev.001/
>>> https://bugs.openjdk.java.net/browse/JDK-8166125
>>> 
>>> - david
>> 
> 



More information about the hotspot-compiler-dev mailing list