Efficiency of dropArguments

[Charles Oliver Nutter]

I do not specialize my test methods, and do drops (or maybe permutes)
to remove all but a couple args.

Mark: Can you post the assembly output for a simple inlined dynamic
call? It would probably tell us a lot.

- Charlie

On Tue, Sep 18, 2012 at 9:27 AM, Mark Roos <mroos at roos.com> wrote:
> I am looking closely at the test portion of my guard with test method
> handle.
> On entry my call stack has zero or more arguments plus the object I wish to
> test on top.  Currently I drop all of the arguments ( leaving the test
> object ),
> bind the value to compare (reference) with and then attach the method which
> extracts
> a field from the test object and identity compares it to the bound value.
>
> Two questions from a low level performance perspective
> Would it help much if I specialize the test method for the number of
> arguments
> thus getting rid of the dropArguments?  Especially since I am keeping the
> TOS.
>
> Does it matter which end I bind the reference value to?  ( TOS vs bottom)
>
> thanks
> mark
> _______________________________________________
> mlvm-dev mailing list
> mlvm-dev at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
>