Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2008-05-14 11:12:35 →
Size: 752
Editor: MaksimAnanjev
Comment:
← Revision 5 as of 2009-09-20 21:54:22 → ⇥
Size: 755
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
[[BR]][[BR]] <<BR>><<BR>>
Line 5: Line 5:
[[BR]][[BR]]
See [:Jitrino_OPT/gc_points: gc_points] for details on managed-pointers reporting algorithm.		 <<BR>><<BR>>
See [[Jitrino_OPT/gc_points| gc_points]] for details on managed-pointers reporting algorithm.
Line 8: Line 8:
implementation file: [http://svn.apache.org/viewvc/harmony/enhanced/drlvm/trunk/vm/jitrino/src/codegenerator/ia32/Ia32GCMap.cpp?view=markup http://svn.apache.org/viewvc/harmony/enhanced/drlvm/trunk/vm/jitrino/src/codegenerator/ia32/Ia32GCMap.cpp] implementation file: [[http://svn.apache.org/viewvc/harmony/enhanced/drlvm/trunk/vm/jitrino/src/codegenerator/ia32/Ia32GCMap.cpp?view=markup|http://svn.apache.org/viewvc/harmony/enhanced/drlvm/trunk/vm/jitrino/src/codegenerator/ia32/Ia32GCMap.cpp]]

'gc_map' LIR transformation prepares a map of all objects and managed pointers operands locations for every instruction that is suspension point. This map is used for GC-enumeration for root-set formation.

The instruction is considered as suspension point if the code execution can be suspended on it. Usually all CALL instructions are considered as suspension points.

See gc_points for details on managed-pointers reporting algorithm.

implementation file: http://svn.apache.org/viewvc/harmony/enhanced/drlvm/trunk/vm/jitrino/src/codegenerator/ia32/Ia32GCMap.cpp

Jitrino_OPT/gcmap (last edited 2009-09-20 21:54:22 by localhost)