RFR: 8165457: [JVMCI] increase InterpreterCodeSize for JVMCI

Christian Thalinger cthalinger at twitter.com
Tue Sep 20 17:59:30 UTC 2016


> On Sep 19, 2016, at 10:21 AM, Doug Simon <doug.simon at oracle.com> wrote:
> 
> 
>> On 06 Sep 2016, at 23:58, Christian Thalinger <cthalinger at twitter.com> wrote:
>> 
>>> 
>>> On Sep 6, 2016, at 11:37 AM, Doug Simon <doug.simon at oracle.com> wrote:
>>> 
>>> 
>>>> On 06 Sep 2016, at 20:14, Christian Thalinger <cthalinger at twitter.com> wrote:
>>>> 
>>>> 
>>>>> On Sep 5, 2016, at 6:49 AM, Doug Simon <doug.simon at oracle.com> wrote:
>>>>> 
>>>>> In jvmci-8, we increased the interpreter code size when JVMCI code is included: 
>>>>> 
>>>>> http://hg.openjdk.java.net/graal/graal-jvmci-8/file/a074ae16281d/src/cpu/x86/vm/templateInterpreter_x86.hpp#l37 
>>>> 
>>>> What about SPARC?  Have we ever seen a problem there?  Or AArch64 for that matter?
>>> 
>>> I’ve only ever seen problems on AMD64. I’ve never seen it on SPARC and have never run on AArch64.
>>> 
>>> The real fix is that the interpreter generator should never have to guess the size of the code buffer it needs but should resize things as needed after generating the interpreter.
>> 
>> Yes, it should.
> 
> In the hope that this gets addressed one day: https://bugs.openjdk.java.net/browse/JDK-8166317 <https://bugs.openjdk.java.net/browse/JDK-8166317>

��
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20160920/404a73c5/attachment.html>


More information about the hotspot-compiler-dev mailing list