Debugging Graal-enabled OpenJDK
Vitaly Davidovich
vitalyd at gmail.com
Mon Oct 3 17:00:18 UTC 2016
Silly question, but are any methods hitting tier 4 (where Graal would be
used) compilation thresholds?
On Monday, October 3, 2016, Andrew Haley <aph at redhat.com
<javascript:_e(%7B%7D,'cvml','aph at redhat.com');>> wrote:
> I'm trying to follow the instructions at
> https://github.com/graalvm/graal-core/blob/master/docs/Debugging.md
>
> My problem is that none of the Graal classes seem to be loaded but
> compilation is still happening. I see:
>
> mx -d vm -XX:+UseJVMCICompiler -cp ~ -XX:+PrintCompilation Hello
> Listening for transport dt_socket at address: 8000
> 7142 1 3 java.lang.String::hashCode (55 bytes)
> 7144 2 3 java.lang.String::charAt (29 bytes)
> 7145 3 3 java.lang.String::length (6 bytes)
> 7145 4 3 java.lang.String::indexOf (70 bytes)
> 7145 5 n 0 java.lang.System::arraycopy (native) (static)
> 7145 8 3 java.lang.Object::<init> (1 bytes)
> 7145 7 3 java.lang.Math::min (11 bytes)
> 7145 6 1 java.lang.ref.Reference::get (5 bytes)
> 7145 9 3 java.lang.String::equals (81 bytes)
> 7145 10 1 java.lang.ThreadLocal::access$400 (5 bytes)
>
> This looks like the usual C1 compilation. If I use -verbose:class
> no Graal classes are listed.
>
> So what do I have to do in order to make the JVM use Graal, so that
> I can debug it?
>
> Andrew.
>
--
Sent from my phone
More information about the graal-dev
mailing list