hg: mlvm/mlvm/hotspot: meth: fix to intrinsic compilation; assembler tweaks for debugging; backtrace filtering
Rémi Forax
forax at univ-mlv.fr
Wed Jul 11 02:20:23 PDT 2012
On 07/10/2012 12:10 PM, Guillaume Laforge wrote:
> It'd be useful for others as well :-)
Yes, for JRuby which is mixed mode (AST walker + bytecode compiler), you
still have to do some
post processing but for Groovy which is compiled only, I think you can
avoid any processing
at runtime if you post process the groovy.jar at compile time (because
Hidden is not a public annotation) :)
Rémi
>
> On Tue, Jul 10, 2012 at 11:12 AM, Rémi Forax <forax at univ-mlv.fr
> <mailto:forax at univ-mlv.fr>> wrote:
>
> On 07/10/2012 10:42 AM, john.r.rose at oracle.com
> <mailto:john.r.rose at oracle.com> wrote:
> > Changeset: 851ca5831589
> > Author: jrose
> > Date: 2012-07-10 01:42 -0700
> > URL: http://hg.openjdk.java.net/mlvm/mlvm/hotspot/rev/851ca5831589
> >
> > meth: fix to intrinsic compilation; assembler tweaks for
> debugging; backtrace filtering
> >
> > ! meth-lazy-7023639.patch
>
> I think backtrace filtering, should be enhanced by adding a new method
> attribute in the bytecode that indicates if a method should be visible
> or not
> when dumping a stacktrace and a display name that should be used
> instead of the bytecode method name.
>
> This may reduce the need of stacktrace post-processing and makes
> Charles
> happy.
>
> Rémi
>
>
> _______________________________________________
> mlvm-dev mailing list
> mlvm-dev at openjdk.java.net <mailto:mlvm-dev at openjdk.java.net>
> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
>
>
>
>
> --
> Guillaume Laforge
> Groovy Project Manager
> SpringSource, a division of VMware
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge <http://twitter.com/glaforge> / Google+
> <https://plus.google.com/u/0/114130972232398734985/posts>
>
>
>
> _______________________________________________
> mlvm-dev mailing list
> mlvm-dev at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
More information about the mlvm-dev
mailing list