Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 1000
-
Component/s: Runtime: Object Model
-
Labels:None
-
Number of attachments :
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.
Issue Links
| This issue depends upon: | ||||
| RVM-290 | Refactor object model so that status word (int) bits are used more intelligently |
|
|
|
There's nothing wrong with supporting a bidirectional object model as an option (generality, has been published before, etc).
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...