hg: mlvm/mlvm/hotspot: meth: fix to intrinsic compilation; assembler tweaks for debugging; backtrace filtering

John Rose john.r.rose at oracle.com
Thu Jul 12 02:11:58 PDT 2012


On Jul 10, 2012, at 2:12 AM, Rémi Forax wrote:

> 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.

I'm don't think we've identified a sweet spot yet, but I encourage people to experiment.  Eventually such a thing could make its way into a JSR (maybe in a MR).

One problem with mixed mode systems is that a method like "executeMyLanguagesInterpretedMethodUntilItGetsCompiled" wants to display a method name based on some value inside the frame itself.  Simply filtering or renaming JVM methods does not cover this case at all.

— John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20120712/d99d2fb7/attachment.html 


More information about the mlvm-dev mailing list