RVM

Avoid back references in java.lang.reflect VMXXX classes

Details

  • Number of attachments :
    0

Description

Currently the patten:

... Method { ...
Method(..)

{ vmMethod = new VMMethod(...); vmMethod.method = this; }

}

... VMMethod { ...
Method method;
... invoke ...

{ method.isAccessible(...) .. }

}

is common in java.lang.reflect. The field holding the Method is non-final therefore we can't optimize the back reference away. It would be much more efficient if when calling VMMethod.invoke the Method was passed as an additional argument.

This effects Constructor too.

Issue Links

is related to

New Feature - A new feature of the product, which has yet to be developed. RVM-517 Reflection optimization

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. RVM-268 Update JikesRVM copies of classes (e.g. Constructor) to match the 1.5/current Classpath API

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • In Progress - This issue is being actively worked on at the moment by the assignee.

Activity

Hide
Permalink
Ian Rogers added a comment -

Patch in r14905.

Show
Ian Rogers added a comment - Patch in r14905.

People

  • Assignee:
    Ian Rogers
    Reporter:
    Ian Rogers
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: