Hotswap - Revision history

Jrose at 20:07, 17 September 2009

2009-09-17T20:07:06Z

2009-09-17T18:32:14Z

‎Background

2009-09-17T18:31:45Z

‎Hotswap

2009-09-17T18:30:57Z

‎Current Status

2009-09-17T18:30:35Z

2009-09-17T18:29:39Z

‎Background

2009-09-17T18:26:23Z

‎Background

2009-09-17T18:25:11Z

‎Background

2009-09-17T18:24:52Z

‎Background

2009-09-17T18:22:46Z

‎Hotswap

@@ Line 2: / Line 2: @@
 Thomas Wuerthinger (wuerthinger@ssw.jku.at) - Sun
-; Slides: [[Image:file.pdf]]
+; Slides: [[Image:Wuerthinger_Hotswap.pdf]]
 == Abstract ==

@@ Line 12: / Line 12: @@
 For a list of publications that were results of this collaboration (topics include SSA form, linear scan register allocation, ABCE, object inlining, escape analysis, compiler graph visualization tools) see:
-[http://wikis.sun.com/display/HotSpotInternals/Publications+JKU JKU Publications]
+[http://wikis.sun.com/display/HotSpotInternals/Publications+JKU JKU HotSpot Publications]
 == Current Status ==

@@ Line 1: / Line 1: @@
 == Hotswap ==
-Thomas Wuerthinger - Sun
+Thomas Wuerthinger (wuerthinger@ssw.jku.at) - Sun
 ; Slides: [[Image:file.pdf]]

@@ Line 15: / Line 15: @@
 == Current Status ==
+[http://wikis.sun.com/display/mlvm/HotSwap Patch + Technical Documentation]
 == Future ==

@@ Line 1: / Line 1: @@
 == Hotswap ==
 Thomas Wuerthinger - Sun
 ; Slides: [[Image:file.pdf]]
-=== Abstract ===
+== Abstract ==
 The current hotswapping mechanism in the HotSpot VM only allows changing the bodies of methods at runtime. We are working on an approach that allows arbitrary changes. This talk is about our experiences implementing a prototype in HotSpot that supports adding and deleting of methods and fields as well as performing changes to the class hierarchy. What are the conditions for dynamic code evolution to have a clear semantics and what kind of changes should be forbidden? What are meaningful applications of dynamic code evolution for Java and their requirements? The talk will conclude with ideas for future work to make dynamic code evolution stable and performant.
-= Background =
+== Background ==
 This project is part of a long-term collaboration between the HotSpot compiler group at Sun Microsystems and the Institute of System Software at the Johannes Kepler University Linz.
@@ Line 17: / Line 14: @@
 [http://wikis.sun.com/display/HotSpotInternals/Publications+JKU JKU Publications]
-= Current Status =
+== Current Status ==
-= Future =
+== Future ==
-= Key Issues for Discussion =
+== Key Issues for Discussion ==
 ''(please expand cooperatively)''

@@ Line 13: / Line 13: @@
 Part of a long-term collaboration between the HotSpot compiler group at Sun Microsystems and the Institute of System Software at the Johannes Kepler University Linz.
-For a list of publications that were results of this collaboration see:
+For a list of publications that were results of this collaboration (topics include SSA form, linear scan register allocation, ABCE, object inlining, escape analysis, compiler graph visualization tools) see:
 [http://wikis.sun.com/display/HotSpotInternals/Publications+JKU JKU Publications]

← Older revision		Revision as of 18:24, 17 September 2009
Line 11:		Line 11:

	= Background =		= Background =
		+	Part of a long-term collaboration between the HotSpot compiler group at Sun Microsystems and the Institute of System Software at the Johannes Kepler University Linz.

		+	For a list of publications that were results of this collaboration see:
		+
		+	[JKU Publications http://wikis.sun.com/display/HotSpotInternals/Publications+JKU]

	= Current Status =		= Current Status =

← Older revision		Revision as of 18:22, 17 September 2009
Line 8:		Line 8:

	=== Abstract ===		=== Abstract ===
		+	The current hotswapping mechanism in the HotSpot VM only allows changing the bodies of methods at runtime. We are working on an approach that allows arbitrary changes. This talk is about our experiences implementing a prototype in HotSpot that supports adding and deleting of methods and fields as well as performing changes to the class hierarchy. What are the conditions for dynamic code evolution to have a clear semantics and what kind of changes should be forbidden? What are meaningful applications of dynamic code evolution for Java and their requirements? The talk will conclude with ideas for future work to make dynamic code evolution stable and performant.

	= Background =		= Background =