OpenJDK 8 on OS/X and XCode 4.
Krystal Mok
rednaxelafx at gmail.com
Mon Nov 7 00:59:04 PST 2011
Hi Mark,
PrintOptoAssembly (for C2, and PrintLIR for C1) only works in a debug build
(which fastdebug is one), where as PrintAssembly works in all builds. If
you need more annotated asm listing then you might want PrintOptoAssembly,
but if you're just after the code instead of the comments then
PrintAssembly should be good enough.
fastdebug is indeed slower (by a little; it'll vary depending on the VM
args, some args are very expensive), on startup and to run.
Regards,
Kris Mok
On Mon, Nov 7, 2011 at 4:51 PM, Mark Roos <mroos at roos.com> wrote:
> From Henri
>
>
> So, I could disable fastdebug in build ?
>
> To charles
> Do we need the fastdebug to get the asm listing? And is it slower
> to run or just start up?
> It seems to run my benchmarks about 30% slower.
>
> Since we have Stephen's with fast debug Henri's could be whatever gives
> the most impressive
> user experience. I have been bouncing around three as it is anyway.
>
> thanks again for the work Henri
> mark
> _______________________________________________
> mlvm-dev mailing list
> mlvm-dev at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20111107/51b6e4bb/attachment.html
More information about the mlvm-dev
mailing list