
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
dependent
|
|
This issue depends upon:
|
|
|
RVM-290 Refactor object model so that status word (int) bits are used more intelligently
|
|
|
|
|
|
|
|
|
Bidirectional object models are well known in the literature and implementations have been made in the RVM by Dayong Gu at McGill and by the guys at ANU. I intend to create a branch so that we can work on creating a stable bidirectional object model to merge back into the trunk.
|
|
Description
|
Bidirectional object models are well known in the literature and implementations have been made in the RVM by Dayong Gu at McGill and by the guys at ANU. I intend to create a branch so that we can work on creating a stable bidirectional object model to merge back into the trunk. |
Show » |
|
I'm skeptical it's actually going to improve on the default sufficiently to justify the added complexity of parsing a bi-directional heap. The usual motivation for a bidirectional object model in Java is optimizing GC tracing operations, but as far as I know, no one has evaluated the bidirectional optimized tracing vs. a properly optimized tracing routine for a unidirectional object model. Been wrong before though...