Primitive type specialization

[Doug Simon]

BTW, we've also just created a page describing various options for debugging Graal, including see generated machine code:

https://wiki.openjdk.java.net/display/Graal/Debugging

On Aug 20, 2013, at 12:04 AM, Christian Thalinger <christian.thalinger at oracle.com> wrote:

> 
> On Aug 18, 2013, at 6:09 AM, Remi Forax <forax at univ-mlv.fr> wrote:
> 
>> Hi guys,
>> I've implemented type specialization for ninal
>> https://github.com/forax/ninal
>> and because I don't like to follow the rules, I don't use node rewriting
>> but a state machine inside each nodes.
>> 
>> It seems to work
>> (you can see the deop/reopt dance when running the example sum.ninal)
>> but I haven't found a way to see the assembly code generated by Truffle
>> to see the code is perfectly specialized or not.
>> 
>> How I can see the assembly code generated by graal ?
> 
> Graal uses HotSpot to manage compiled code so all of the usual printing flags work:
> 
> -XX:+PrintAssembly, -XX:+PrintNMethods, -XX:CompileCommand=print,foo::bar
> 
> -- Chris
> 
>> 
>> Rémi
>> 
>> 
>