You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by na...@apache.org on 2007/04/03 16:10:52 UTC
svn commit: r525159 [4/5] - in /harmony/standard/site: docs/
docs/subcomponents/classlibrary/ docs/subcomponents/drlvm/ xdocs/
xdocs/subcomponents/classlibrary/ xdocs/subcomponents/drlvm/
Modified: harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html?view=diff&rev=525159&r1=525158&r2=525159
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html Tue Apr 3 07:10:50 2007
@@ -29,126 +29,84 @@
<h1>
<a id="top" name="top"></a>DRLVM Jitrino Just-in-time Compiler
</h1>
- <p class="TOCHeading">
- <a href="#Revision_History">Revision History</a>
- </p>
- <p class="TOCHeading">
- <a href="#About_this_document">1. About this Document</a>
- </p>
- <p class="TOC">
- <a href="#Purpose">1.1 Purpose</a>
- </p>
- <p class="TOC">
- <a href="#Intended_Audience">1.2 Intended Audience</a>
- </p>
- <p class="TOC">
- <a href="#Using_this_document">1.3 Using This Document</a>
- </p>
- <p class="TOC">
- <a href="#Conventions_and_Symbols">1.4 Conventions and Symbols</a>
- </p>
- <p class="TOCHeading">
- <a href="#Overview">2. Overview</a>
- </p>
- <p class="TOC">
- <a href="#Key_features">2.1 Key Features</a>
- </p>
- <p class="TOC">
- <a href="#Compilation_Overview">2.2 About Compilation</a>
- </p>
- <p class="TOCHeading">
- <a href="#OPT">3. Jitrino.OPT</a>
- </p>
- <p class="TOC">
- <a href="#OPT_Architecture">3.1 Architecture</a>
- </p>
- <blockquote>
- <p class="TOC">
- <a href="#PMF">3.1.1 Pipeline Management Framework</a>
- </p>
- <p class="TOC">
- <a href="#OPT_Components">3.1.2 Logical Components</a>
- </p>
- <p class="TOC">
- <a href="#IR">3.1.3 Intermediate Representations</a>
- </p>
- </blockquote>
- <p class="TOC">
- <a href="#OPT_Processes">3.2 Processes</a>
- </p>
- <blockquote>
- <p class="TOC">
- <a href="#Bytecode_Translation">3.2.1 Bytecode Translation</a>
- </p>
- <p class="TOC">
- <a href="#HIR_Optimizations">3.2.2 High-level Optimizations</a>
- </p>
- <p class="TOC">
- <a href="#CodeSelection">3.2.3 Code Selection</a>
- </p>
- <p class="TOC">
- <a href="#Code_Generation">3.2.4 Code generation</a>
- </p>
- </blockquote>
- <p class="TOCHeading">
- <a href="#JET">4. Jitrino.JET</a>
- </p>
- <p class="TOC">
- <a href="#JET_Architecture">4.1 Architecture</a>
- </p>
- <blockquote>
- <p class="TOC">
- <a href="#JET_Runtime">4.1.1 Run-time Support</a>
- </p>
- </blockquote>
- <p class="TOC">
- <a href="#JET_Processes">4.2 Processes</a>
- </p>
- <blockquote>
- <p class="TOC">
- <a href="#Baseline_Compilation">4.2.1 Baseline Compilation</a>
- </p>
- </blockquote>
- <p class="TOCHeading">
- <a href="#JIT_utilities">5. Utilities</a>
- </p>
- <p class="TOC">
- <a href="#Memory_Manager">5.1 Memory Manager</a>
- </p>
- <p class="TOC">
- <a href="#Timers">5.2 Counters and Timers</a>
- </p>
- <p class="TOC">
- <a href="#JIT_logging">5.3 Logging</a>
- </p>
- <p class="TOC">
- <a href="#CFG">5.4 Control Flow Graph</a>
- </p>
- <blockquote>
- <p class="TOC">
- <a href="#CFGStructures">5.4.1 CFG structures</a>
- </p>
- <p class="TOC">
- <a href="#CFGAlgorithms">5.4.2 Graph algorithms</a>
- </p>
- <p class="TOC">
- <a href="#DominatorTree">5.4.3 Dominator Tree</a>
- </p>
- <p class="TOC">
- <a href="#LoopTree">5.4.4 Loop Tree</a>
- </p>
- </blockquote>
- <p class="TOCHeading">
- <a href="#Interfaces">6. Public Interfaces</a>
- </p>
- <p class="TOC">
- <a href="#JIT_VM">5.1 JIT_VM Interface</a>
- </p>
- <p class="TOC">
- <a href="#JIT_EM">5.2 JIT_EM Interface</a>
- </p>
- <p class="TOCHeading">
- <a href="#References">6. References</a>
+ <ol id="TOC">
+ <li><a href="#Revision_History">Revision History</a></li>
+ <li><a href="#About_this_document">About This Document</a>
+ <ol>
+ <li><a href="#Purpose">Purpose</a</li>
+ <li><a href="#Intended_Audience">Intended Audience</a></li>
+ <li><a href="#Using_this_document">Using This Document</a></li>
+ <li><a href="#Conventions_and_Symbols">Conventions and Symbols</a></li>
+ </ol>
+ </li>
+ <li><a href="#Overview">Overview</a>
+ <ol>
+ <li><a href="#Key_features">Key Features</a></li>
+ <li><a href="#Compilation_Overview">About Compilation</a></li>
+ </ol>
+ </li>
+ <li><a href="#OPT">Jitrino.OPT</a>
+ <ol>
+ <li><a href="#OPT_Architecture">Architecture</a>
+ <ol>
+ <li><a href="#PMF">Pipeline Management Framework</a></li>
+ <li><a href="#OPT_Components">Logical Components</a></li>
+ <li><a href="#IR">Intermediate Representations</a></li>
+ </ol>
+ </li>
+ <li><a href="#OPT_Processes">Processes</a>
+ <ol>
+ <li><a href="#Bytecode_Translation">Bytecode Translation</a></li>
+ <li><a href="#HIR_Optimizations">High-level Optimizations</a></li>
+ <li><a href="#CodeSelection">Code Selection</a></li>
+ <li><a href="#Code_Generation">Code generation</a></li>
+ </ol>
+ </li>
+ </ol>
+ </li>
+ <li><a href="#JET">Jitrino.JET</a>
+ <ol>
+ <li><a href="#JET_Architecture">Architecture</a>
+ <ol>
+ <li><a href="#JET_Runtime">Run-time Support</a></li>
+ </ol>
+ </li>
+ <li><a href="#JET_Processes">Processes</a>
+ <ol>
+ <li><a href="#Baseline_Compilation">Baseline Compilation</a></li>
+ </ol>
+ </li>
+ </ol>
+ </li>
+ <li><a href="#JIT_utilities">Utilities</a>
+ <ol>
+ <li><a href="#Memory_Manager">Memory Manager</a></li>
+ <li><a href="#Timers">Counters and Timers</a></li>
+ <li><a href="#JIT_logging">Logging</a>
+ <ol>
+ <li><a href="#CFG Visualization">CFG Visualization</a></li>
+ </ol>
+ </li>
+ <li><a href="#CFG">Control Flow Graph</a>
+ <ol>
+ <li><a href="#CFGStructures">CFG structures</a></li>
+ <li><a href="#CFGAlgorithms">Graph algorithms</a></li>
+ <li><a href="#DominatorTree">Dominator Tree</a></li>
+ <li><a href="#LoopTree">Loop Tree</a></li>
+ </ol>
+ </li>
+ </ol>
+ </li>
+ <li><a href="#Interfaces">Public Interfaces</a>
+ <ol>
+ <li><a href="#JIT_VM">JIT_VM Interface</a></li>
+ <li><a href="#JIT_EM">JIT_EM Interface</a></li>
+ </ol>
+ </li>
+ <li><a href="#References">References</a></li>
+ </ol>
+
+
</p>
<h1>
<a id="Revision_History" name="Revision_History"></a>Revision History
@@ -178,11 +136,11 @@
</tr>
</table>
<h1>
- <a id="About_this_document" name="About_this_document"></a>1. About
- this document
+ <a id="About_this_document" name="About_this_document"></a>About
+ This document
</h1>
<h2>
- <a id="Purpose" name="Purpose"></a>1.1 Purpose
+ <a id="Purpose" name="Purpose"></a>Purpose
</h2>
<p>
This document describes the internal structure of the Jitrino
@@ -197,7 +155,7 @@
Guide</a> supplied with the VM source code package.
</p>
<h2>
- <a id="Intended_Audience" name="Intended_Audience"></a>1.2 Intended
+ <a id="Intended_Audience" name="Intended_Audience"></a>Intended
Audience
</h2>
<p>
@@ -209,7 +167,7 @@
compilation and optimization algorithms.
</p>
<h2>
- <a id="Using_this_document" name="Using_this_document"></a>1.3 Using
+ <a id="Using_this_document" name="Using_this_document"></a>Using
This Document
</h2>
<p>
@@ -264,7 +222,7 @@
</li>
</ul>
<h2>
- <a id="Conventions_and_Symbols" name="Conventions_and_Symbols"></a>1.4
+ <a id="Conventions_and_Symbols" name="Conventions_and_Symbols"></a>
Conventions and Symbols
</h2>
<p>
@@ -275,7 +233,7 @@
<a href="#top">Back to Top</a>
</p>
<h1>
- <a id="Overview" name="Overview"></a>2. Overview
+ <a id="Overview" name="Overview"></a>Overview
</h1>
<p>
Jitrino is the code name for the just-in-time (JIT) compiler [<a
@@ -313,7 +271,7 @@
<a href="#top">Back to Top</a>
</p>
<h2>
- <a id="Key_features" name="Key_features"></a>2.1 Key features
+ <a id="Key_features" name="Key_features"></a>Key Features
</h2>
<p>
Key features of the JIT compiler include:
@@ -358,7 +316,7 @@
<a href="#top">Back to Top</a>
</p>
<h2>
- <a id="Compilation_Overview" name="Compilation_Overview"></a>2.2 About
+ <a id="Compilation_Overview" name="Compilation_Overview"></a>About
the Compilation Process
</h2>
<p>
@@ -401,14 +359,11 @@
focus on the following:
</p>
<ol>
- <li>
- <p>
- The run-time environment bytecode is translated into the
+ <li>The run-time environment bytecode is translated into the
high-level intermediate representation (HIR) by the Java<a
href="#*">*</a> bytecode translator and then optimized by the
high-level optimizer. HIR and the optimizer make up the
language- and platform-independent part of the Jitrino.OPT.
- </p>
<p class="note">
Note
</p>
@@ -440,17 +395,17 @@
<a href="#top">Back to Top</a>
</p>
<h1>
- <a id="OPT" name="OPT"></a>3. Jitrino.OPT
+ <a id="OPT" name="OPT"></a>Jitrino.OPT
</h1>
<h2>
- <a id="OPT_Architecture" name="OPT_Architecture"></a>3.1 Architecture
+ <a id="OPT_Architecture" name="OPT_Architecture"></a>Architecture
</h2>
<p>
This part of the document describes the internals of the optimizing
compiler Jitrino.OPT.
</p>
<h3>
- <a id="PMF" name="PMF"></a>3.1.1 Pipeline Management Framework
+ <a id="PMF" name="PMF"></a>Pipeline Management Framework
</h3>
<p>
The pipeline management framework (PMF) defines how the compilation
@@ -487,7 +442,7 @@
<a href="#top">Back to Top</a>
</p>
<h3>
- <a id="OPT_Components" name="OPT_Components"></a>3.1.2 Logical
+ <a id="OPT_Components" name="OPT_Components"></a>Logical
Components
</h3>
<p>
@@ -514,7 +469,7 @@
address.
</p>
<p>
- For details on the conversion process, see section 3.2.1 <a
+ For details on the conversion process, see section <a
href="#Bytecode_Translation">Bytecode Translation</a>.
</p>
</dd>
@@ -529,7 +484,7 @@
href="#*">*</a> and CLI programs is used. The optimizer performs
a series of transformation passes to optimize the incoming
high-level intermediate representation. For a description of
- applied transformations, see section 3.2.2 <a
+ applied transformations, see section <a
href="#HIR_Optimizations">High-level Optimizations</a>.
</p>
<p>
@@ -544,7 +499,7 @@
whole method, basic blocks, and instructions. During code
selection, the selector uses the callback interfaces to
translate these entities from HIR to LIR. See section <a
- href="#CodeSelection">3.2.3 Code Selection</a> for details on
+ href="#CodeSelection">Code Selection</a> for details on
the process.
</p>
</dd>
@@ -558,7 +513,7 @@
accepts the HIR information via the <a href="#CodeSelector">code
selector</a> callback interfaces. For details on how the
resulting code is produced, see section <a
- href="#Code_Generation">3.2.4 Code Generation</a>.
+ href="#Code_Generation">Code Generation</a>.
</p>
<p>
The code generator also performs several auxiliary operations,
@@ -586,7 +541,7 @@
<a href="#top">Back to Top</a>
</p>
<h3>
- <a id="IR" name="IR"></a>3.1.3 Internal Representations
+ <a id="IR" name="IR"></a>Internal Representations
</h3>
<p>
An intermediate representation (IR) is an internal compiler
@@ -650,7 +605,7 @@
</p>
<p>
Both HIR and LIR use a common Control Flow Graph structures and its
- algorithms; see section 5.4 <a href="#CFG">Control Flow Graph</a> for
+ algorithms; see section <a href="#CFG">Control Flow Graph</a> for
the details. This section describes the two intermediate
representations currently used in Jitrino in greater detail.
</p>
@@ -701,14 +656,14 @@
<a href="#top">Back to Top</a>
</p>
<h2>
- <a id="OPT_Processes" name="OPT_Processes"></a>3.2 Processes
+ <a id="OPT_Processes" name="OPT_Processes"></a>Processes
</h2>
<p>
This part of the document describes the key processes that go inside
the Jitrino optimizing compiler.
</p>
<h3>
- <a id="Bytecode_Translation" name="Bytecode_Translation"></a>3.2.1
+ <a id="Bytecode_Translation" name="Bytecode_Translation"></a>
Bytecode Translation
</h3>
<p>
@@ -733,7 +688,7 @@
</li>
</ol>
<h3>
- <a id="HIR_Optimizations" name="HIR_Optimizations"></a>3.2.2
+ <a id="HIR_Optimizations" name="HIR_Optimizations"></a>
High-level Optimizations
</h3>
<p>
@@ -1125,7 +1080,7 @@
<a href="#top">Back to Top</a>
</p>
<h3>
- <a name="CodeSelection" id="CodeSelection"></a>3.2.3 Code Selection
+ <a name="CodeSelection" id="CodeSelection"></a>Code Selection
</h3>
<p>
After the optimization passes, HIR is translated to LIR. This code
@@ -1229,8 +1184,8 @@
<a href="#top">Back to Top</a>
</p>
<h3>
- <a id="Code_Generation" name="Code_Generation"></a>3.2.4 Code
- generation
+ <a id="Code_Generation" name="Code_Generation"></a>Code
+ Generation
</h3>
<p>
The code generation process is specific to the pluggable code
@@ -1486,10 +1441,10 @@
<a href="#top">Back to Top</a>
</p>
<h1>
- <a id="JET" name="JET"></a>4. JITRINO.JET
+ <a id="JET" name="JET"></a>JITRINO.JET
</h1>
<h2>
- <a id="JET_Architecture" name="JET_Architecture"></a>4.1 Architecture
+ <a id="JET_Architecture" name="JET_Architecture"></a>Architecture
</h2>
<p>
The Jitrino.JET baseline compiler is the Jitrino subcomponent used for
@@ -1499,7 +1454,7 @@
registers.
</p>
<h3>
- <a id="JET_Runtime" name="JET_Runtime"></a>4.1.1 Run-time Support
+ <a id="JET_Runtime" name="JET_Runtime"></a>Run-time Support
</h3>
<p>
During the code generation phase, the state of the method's operand
@@ -1540,10 +1495,10 @@
<a href="#top">Back to Top</a>
</p>
<h2>
- <a id="JET_Processes" name="JET_Processes"></a>4.2 Processes
+ <a id="JET_Processes" name="JET_Processes"></a>Processes
</h2>
<h3>
- <a id="Baseline_Compilation" name="Baseline_Compilation"></a>4.2.1
+ <a id="Baseline_Compilation" name="Baseline_Compilation"></a>
Baseline Compilation
</h3>
<p>
@@ -1557,8 +1512,8 @@
and generates native code during the second.
</p>
<p style="text-align:center">
- <img src="images/bytecode_to_native.gif"
- alt="Example of two-pass compilation process" />
+ <img src="images/bytecode_to_native.gif"
+ alt="Example of two-pass compilation process" />
</p>
<p class="special">
Figure 4. Baseline Compilation Path
@@ -1619,8 +1574,8 @@
fall-through from BB2.
</p>
<p style="text-align: center">
- <img src="images/reference_count.gif"
- alt="Example of reference counters reached from different basic blocks." />
+ <img src="images/reference_count.gif"
+ alt="Example of reference counters reached from different basic blocks." />
</p>
<p class="special">
Figure 5. Reference Count for Basic Blocks
@@ -1665,7 +1620,7 @@
<a href="#top">Back to Top</a>
</p>
<h1>
- <a id="JIT_utilities" name="JIT_utilities"></a>5. Utilities
+ <a id="JIT_utilities" name="JIT_utilities"></a>Utilities
</h1>
<p>
The JIT compiler relies on the following utilities:
@@ -1708,7 +1663,7 @@
<a href="#top">Back to Top</a>
</p>
<h2>
- <a id="Memory_Manager" name="Memory_Manager"></a>5.1 Memory Manager
+ <a id="Memory_Manager" name="Memory_Manager"></a>Memory Manager
</h2>
<p>
In the Jitrino.OPT compiler, memory allocation is done using custom
@@ -1828,7 +1783,7 @@
<a href="#top">Back to Top</a>
</p>
<h2>
- <a id="Timers" name="Timers"></a>5.2 Counters and Timers
+ <a id="Timers" name="Timers"></a>Counters and Timers
</h2>
<p>
Jitrino maintains <em>counters</em> to collect statistics. A counter
@@ -1870,7 +1825,7 @@
<a href="#top">Back to Top</a>
</p>
<h2>
- <a id="JIT_logging" name="JIT_logging"></a>5.3 Logging System
+ <a id="JIT_logging" name="JIT_logging"></a>Logging System
</h2>
<p>
The Jitrino logging system does the following:
@@ -1992,8 +1947,7 @@
<pre class="exampletext">
-XDjit.arg.log=ct,irdump
</pre>
- <h3>
- 5.3.1 CFG Visualization
+ <h3><a name="CFG Visualization" id="CFG Visualization" ></a>CFG Visualization
</h3>
<p>
Debugging the JIT requires information on the compilation inter-stage
@@ -2002,7 +1956,7 @@
Jitrino compiler enables generation of <em>dot</em> files representing
the control flow graph at both IR levels. The text .dot files can be
converted into descriptive pictures, which represent the CFG
- graphically; see <a href="#IR">section 3.1.3 Internal
+ graphically; see <a href="#IR">section Internal
Representations</a> for an example of graphically visualized code. A
variety of graph visualization tools are available for dot files
conversion, such as Graphviz <a href="#Graphviz_ref">[6</a>].
@@ -2021,7 +1975,7 @@
<a href="#top">Back to Top</a>
</p>
<h2>
- <a id="CFG" name="CFG"></a>5.4 Control Flow Graph
+ <a id="CFG" name="CFG"></a>Control Flow Graph
</h2>
<p>
The high-level and low-level intermediate representations use a
@@ -2080,7 +2034,7 @@
branches.
</p>
<h3>
- <a name="CFGStructures" id="CFGStructures"></a>5.4.1 CFG structures
+ <a name="CFGStructures" id="CFGStructures"></a>CFG Structures
</h3>
<p>
The CFG structures are nodes, edges and instructions represented as
@@ -2209,7 +2163,7 @@
</dd>
</dl>
<h3>
- <a id="CFGAlgorithms" name="CFGAlgorithms"></a>5.4.2 Graph algorithms
+ <a id="CFGAlgorithms" name="CFGAlgorithms"></a>Graph Algorithms
</h3>
<p>
The current CFG implementation provides the following graph
@@ -2242,7 +2196,7 @@
<code>ControlFlowGraph.h</code> file using Doxygen.
</p>
<h3>
- <a id="DominatorTree" name="DominatorTree"></a>5.4.3 Dominator Tree
+ <a id="DominatorTree" name="DominatorTree"></a>Dominator Tree
</h3>
<p>
A dominator tree represents (post)dominance information computed for a
@@ -2266,7 +2220,7 @@
longer reflect the current state of the control flow graph.
</p>
<h3>
- <a id="LoopTree" name="LoopTree"></a> 5.4.4 Loop Tree
+ <a id="LoopTree" name="LoopTree"></a>Loop Tree
</h3>
<p>
A loop tree contains information about loops in control flow graph. It
@@ -2294,7 +2248,7 @@
<a href="#top">Back to Top</a>
</p>
<h1>
- <a id="Interfaces" name="Interfaces"></a>6. Public Interfaces
+ <a id="Interfaces" name="Interfaces"></a>Public Interfaces
</h1>
<p>
This section describes the interfaces that the JIT compiler exports to
@@ -2304,7 +2258,7 @@
JIT to enumerate live references.
</p>
<h2>
- <a id="JIT_VM" name="JIT_VM"></a>6.1 JIT_VM Interface
+ <a id="JIT_VM" name="JIT_VM"></a>JIT_VM Interface
</h2>
<p>
This interface comprises functions that the JIT compiler exports for
@@ -2395,7 +2349,7 @@
</li>
</ul>
<p>
- For more information about the stack, see section <em>3.4 Stack
+ For more information about the stack, see section <em>Stack
Support</em> in the <a href="developers_guide.html">Developer's
Guide</a>.
</p>
@@ -2453,7 +2407,7 @@
<a href="#top">Back to Top</a>
</p>
<h2>
- <a name="JIT_EM" id="JIT_EM"></a>6.2 JIT_EM Interface
+ <a name="JIT_EM" id="JIT_EM"></a>JIT_EM Interface
</h2>
<p>
The JIT compiler exports this interface to support the execution
@@ -2482,7 +2436,7 @@
<a href="#top">Back to Top</a>
</p>
<h1>
- <a id="References" name="References"></a>7. References
+ <a id="References" name="References"></a>References
</h1>
<p>
This section lists the external references to various sources used in
@@ -2530,11 +2484,7 @@
<p class="backtotop">
<a href="#Top">Back to Top</a>
</p>
- <p class="backtotop">
-
- </p>
- <p>
- (C) Copyright 2005-2006 Intel Corporation
+ <p>(C) Copyright 2005-2006 Intel Corporation
</p>
<p>
<a id="*" name="*">*</a> Other brands and names are the property of
@@ -2542,5 +2492,6 @@
</p>
</body>
</html>
+
Modified: harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino_PMF.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino_PMF.html?view=diff&rev=525159&r1=525158&r2=525159
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino_PMF.html (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino_PMF.html Tue Apr 3 07:10:50 2007
@@ -32,82 +32,55 @@
<h1><a id="top"
name="top"></a>Jitrino Pipeline Management Framework</h1>
- <p class="TOCHeading"><a href="#Revision_History">Revision
- History</a></p>
-
- <p class="TOCHeading"><a href="#About_This_Document">1. About
- This Document</a></p>
-
- <p class="TOC"><a href="#Purpose">1.1 Purpose</a></p>
-
- <p class="TOC"><a href="#Intended_Audience">1.2 Intended
- Audience</a></p>
-
- <p class="TOC"><a href="#Documentation_Conventions">1.3
- Documentation Conventions</a></p>
-
- <p class="TOCHeading"><a href="#Overview">2. Overview</a></p>
-
- <p class="TOC"><a href="#Key_Elements">2.1 Key Elements</a></p>
-
- <p class="TOC"><a href="#Implementation_Notes">2.2
- Implementation Notes</a></p>
-
- <p class="TOC"><a href="#Pipeline_Life-cycle">2.3 Pipeline
- Life-cycle</a></p>
-
- <blockquote>
- <p class="TOC"><a href="#Initialization">2.3.1
- Initialization</a></p>
-
- <p class="TOC"><a href="#Method_Compilation">2.3.2 Method
- Compilation</a></p>
-
- <p class="TOC"><a href="#De-initialization">2.3.3
- De-initialization</a></p>
- </blockquote>
-
- <p class="TOCHeading"><a href="#Command-line_Interface">3.
- Command-line Interface</a></p>
-
- <p class="TOCHeading"><a href="#PMF_Commands">4. PMF
- Commands</a></p>
-
- <p class="TOC"><a href="#Path_Definition">4.1 Path
- Definition</a></p>
-
- <p class="TOC"><a href="#Filter_Definition">4.2 Filter
- Definition</a></p>
-
- <p class="TOC"><a href="#Argument_Definition">4.3 Argument
- Definition</a></p>
-
- <p class="TOCHeading"><a href="#Logging_System">5. Logging
- System</a></p>
-
- <p class="TOC"><a href="#Defining_Streams">5.1 Defining
- Streams</a></p>
-
- <p class="TOC"><a href="#Assigning_a_Stream_to_a_File">5.2
- Assigning a Stream to a File</a></p>
-
- <blockquote>
- <p class="TOC"><a href="#Using_Filename_Masks">5.2.1 Using
- Filename Masks</a></p>
-
- <p class="TOC"><a href="#Filename_Review">5.2.2 Filename
- Review</a></p>
- </blockquote>
-
- <p class="TOC"><a href="#Using_Streams">5.3 Using
- Streams</a></p>
-
- <p class="TOCHeading"><a href="#Appendix">6. Appendix</a></p>
-
- <p class="TOC">
- <a href="#General_Command-line_Syntax_Specification">6.1
- General Command-line Syntax Specification</a></p>
-
+ <ol id="TOC">
+ <li><a href="#Revision_History">Revision History</a></li>
+ <li><a href="#About_This_Document">About This Document</a>
+ <ol>
+ <li><a href="#Purpose">Purpose</a></li>
+ <li><a href="#Intended_Audience">Intended Audience</a></li>
+ <li><a href="#Documentation_Conventions">Documentation Conventions</a></li>
+ </ol>
+ </li>
+ <li><a href="#Overview">Overview</a>
+ <ol>
+ <li><a href="#Key_Elements">Key Elements</a></li>
+ <li><a href="#Implementation_Notes">Implementation Notes</a></li>
+ <li><a href="#Pipeline_Life-cycle">Pipeline Life-cycle</a>
+ <ol>
+ <li><a href="#Initialization">Initialization</a></li>
+ <li><a href="#Method_Compilation">Method Compilation</a></li>
+ <li><a href="#De-initialization">De-initialization</a></li>
+ </ol>
+ </li>
+ </ol>
+ </li>
+ <li><a href="#Command-line_Interface">Command-line Interface</a></li>
+ <li><a href="#PMF_Commands">PMF Commands</a>
+ <ol>
+ <li><a href="#Path_Definition">Path Definition</a></li>
+ <li><a href="#Filter_Definition">Filter Definition</a></li>
+ <li><a href="#Argument_Definition">Argument Definition</a></li>
+ </ol>
+ </li>
+ <li><a href="#Logging_System">Logging System</a>
+ <ol>
+ <li><a href="#Defining_Streams">Defining Streams</a></li>
+ <li><a href="#Assigning_a_Stream_to_a_File">Assigning a Stream to a File</a>
+ <ol>
+ <li><a href="#Using_Filename_Masks">Using Filename Masks</a></li>
+ <li><a href="#Filename_Review">Filename Review</a></li>
+ </ol>
+ </li>
+ <li><a href="#Using_Streams">Using Streams</a></li>
+ </ol>
+ </li>
+ <li><a href="#Appendix">Appendix</a>
+ <ol>
+ <li><a href="#General_Command-line_Syntax_Specification">
+ General Command-line Syntax Specification</a></li>
+ </ol>
+ </li>
+ </ol>
<h1><a name="Revision_History"
id="Revision_History"></a>Revision History</h1>
@@ -133,10 +106,10 @@
</table>
<h1><a name="About_This_Document"
- id="About_This_Document"></a>1. About This Document</h1>
+ id="About_This_Document"></a>About This Document</h1>
<h2><a name="Purpose"
- id="Purpose"></a>1.1 Purpose</h2>
+ id="Purpose"></a>Purpose</h2>
<p>The document is a comprehensive description of the
<i>pipeline management framework</i> that provides complete
@@ -152,7 +125,7 @@
the component description.</p>
<h2><a id="Intended_Audience"
- name="Intended_Audience"></a>1.2 Intended Audience</h2>
+ name="Intended_Audience"></a>Intended Audience</h2>
<p>The target audience for the document includes a wide
community of DRLVM developers interested in understanding
@@ -162,7 +135,7 @@
compilation.</p>
<h2><a id="Documentation_Conventions"
- name="Documentation_Conventions"></a>1.3 Documentation
+ name="Documentation_Conventions"></a>Documentation
Conventions</h2>
<p>This document uses the <a href="../../documentation/conventions.html">unified
@@ -171,7 +144,7 @@
<p class="backtotop"><a href="#top">Back to Top</a></p>
<h1><a id="Overview"
- name="Overview"></a>2. Overview</h1>
+ name="Overview"></a>Overview</h1>
<p>The document contains the detailed description of the
Jitrino pipeline management framework (PMF). For a high-level
@@ -179,7 +152,7 @@
document</a>.</p>
<h2><a id="Key_Elements"
- name="Key_Elements"></a>2.1 Key Elements</h2>
+ name="Key_Elements"></a>Key Elements</h2>
<p>This section contains a detailed description of the PMF key
elements.</p>
@@ -318,7 +291,7 @@
<p class="backtotop"><a href="#top">Back to Top</a></p>
<h2><a id="Implementation_Notes"
- name="Implementation_Notes"></a>2.2 Implementation
+ name="Implementation_Notes"></a>Implementation
Notes</h2>
<p>When using the PMF implementation, please note the
@@ -344,10 +317,10 @@
<p class="backtotop"><a href="#top">Back to Top</a></p>
<h2><a id="Pipeline_Life-Cycle"
- name="Pipeline_Life-cycle"></a>2.3 Pipeline Life-cycle</h2>
+ name="Pipeline_Life-cycle"></a>Pipeline Life-cycle</h2>
<h3><a id="Initialization"
- name="Initialization"></a>2.3.1 Initialization</h3>
+ name="Initialization"></a>Initialization</h3>
<p>The common pipeline is created at the JIT initialization.
All other pipelines are created just before their first use.
@@ -375,7 +348,7 @@
prepared during the initialization phase.</p>
<h3><a id="Method_Compilation"
- name="Method_Compilation"></a>2.3.2 Method Compilation</h3>
+ name="Method_Compilation"></a>Method Compilation</h3>
<p>At this stage, the compiler selects the pipeline for the
given method using the filter expression in the method filter
@@ -391,7 +364,7 @@
<code>run()</code> method in each object, and destroys it.</p>
<h3><a id="De-initialization"
- name="De-initialization"></a>2.3.3 De-initialization</h3>
+ name="De-initialization"></a>De-initialization</h3>
<p>At the JIT de-initialization phase all created pipelines are
destroyed. The <code>Action::deinit()</code> method is called
@@ -400,7 +373,7 @@
<p class="backtotop"><a href="#top">Back to Top</a></p>
<h1><a id="Command-line_Interface"
- name="Command-line_Interface"></a>3. Command-line
+ name="Command-line_Interface"></a>Command-line
Interface</h1>
<p>The <i>command-line interface</i> is based on system
@@ -507,7 +480,7 @@
<p class="backtotop"><a href="#top">Back to Top</a></p>
<h1><a id="PMF_Commands"
- name="PMF_Commands"></a>4. PMF Commands</h1>
+ name="PMF_Commands"></a>PMF Commands</h1>
<p>To control the JIT compilation process, PMF uses
<a href="#Path_Definition">path definition</a>,
@@ -516,7 +489,7 @@
commands.</p>
<h2><a id="Path_Definition"
- name="Path_Definition"></a>4.1 Path Definition</h2>
+ name="Path_Definition"></a>Path Definition</h2>
<p>A pipeline can be described as an ordered set of terminal
leafs of a path tree. The tree is a purely abstract concept
@@ -604,7 +577,7 @@
<p class="backtotop"><a href="#top">Back to Top</a></p>
<h2><a id="Filter_Definition"
- name="Filter_Definition"></a>4.2 Filter Definition</h2>
+ name="Filter_Definition"></a>Filter Definition</h2>
<p>To define a filter, use the following command format:</p>
<pre>
@@ -698,7 +671,7 @@
<p class="backtotop"><a href="#top">Back to Top</a></p>
<h2><a id="Argument_Definition"
- name="Argument_Definition"></a>4.3 Argument Definition</h2>
+ name="Argument_Definition"></a>Argument Definition</h2>
<p>To control the actions behavior, PMF supports an action
parameters passing convention. The parameter definition command
@@ -904,14 +877,14 @@
<p class="backtotop"><a href="#top">Back to Top</a></p>
<h1><a id="Logging_System"
- name="Logging_System"></a>5. Logging System</h1>
+ name="Logging_System"></a>Logging System</h1>
<p>The <i>logging system</i> supports diagnostic messages from
pipeline actions. The VM property mechanism fully controls the
system.</p>
<h2><a
- name="Defining_Streams"></a>5.1 Defining Streams</h2>
+ name="Defining_Streams"></a>Defining Streams</h2>
<p>A set of <i>log streams</i> is used for logging in Jitrino.
Each log stream has a name. The name of the log stream is not
@@ -1035,7 +1008,7 @@
<p class="backtotop"><a href="#top">Back to Top</a></p>
<h2><a id="Assigning_a_Stream_to_a_File"
- name="Assigning_a_Stream_to_a _File"></a>5.2 Assigning a
+ name="Assigning_a_Stream_to_a _File"></a>Assigning a
Stream to a File</h2>
<p>To assign a stream to a file, use the following command
@@ -1113,7 +1086,7 @@
contains the <code>%thread%</code> macro, this file is
thread-specific and access to it is not synchronized.</p>
- <h3><a name="Using_Filename_Masks"></a>5.2.1 Using Filename
+ <h3><a name="Using_Filename_Masks"></a>Using Filename
Masks</h3>
<p>For all streams, the following default filename mask is
@@ -1195,7 +1168,7 @@
is the name of the action and <<b>action_nb</b>> is the
sequential number of the action in the current pipeline.</p>
- <h3><a name="Filename_Review"></a>5.2.2 Filename Review</h3>
+ <h3><a name="Filename_Review"></a>Filename Review</h3>
<p>Names of all open stream files are reviewed at the beginning
of method compilation, because the stream file name can depend
@@ -1223,7 +1196,7 @@
<p class="backtotop"><a href="#top">Back to Top</a></p>
- <h2><a name="Using_Streams"></a>5.3 Using Streams</h2>
+ <h2><a name="Using_Streams"></a>Using Streams</h2>
<p>A typical usage pattern for Jitrino action is the
following:</p>
@@ -1249,10 +1222,10 @@
<p class="backtotop"><a href="#top">Back to Top</a></p>
<h1><a id="Appendix"
- name="Appendix"></a>6. Appendix</h1>
+ name="Appendix"></a>Appendix</h1>
<h2><a id="General_Command-line_Syntax_Specification"
- name="General_Command-line_Syntax_Specification"></a>6.1
+ name="General_Command-line_Syntax_Specification"></a>
General Command-line Syntax Specification</h2>
<pre>
<cmd> : <prefix> <filter def>
Modified: harmony/standard/site/xdocs/subcomponents/drlvm/ThreadManager.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/ThreadManager.html?view=diff&rev=525159&r1=525158&r2=525159
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/ThreadManager.html (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/ThreadManager.html Tue Apr 3 07:10:50 2007
@@ -1,10 +1,10 @@
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements. See the NOTICE file distributed with
+ contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
- the License. You may obtain a copy of the License at
+ the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
@@ -30,55 +30,55 @@
<h1>
<a id="top" name="top"></a>Thread Manager
</h1>
- <ol class="TOC">
- <li><a href="#RevisionHistory">1. Revision History</a></li>
- <li><a href="#About_This_Document">2. About this Document</a>
+ <ol id="TOC">
+ <li><a href="#RevisionHistory">Revision History</a></li>
+ <li><a href="#About_This_Document">About This Document</a>
<ol>
- <li><a href="#Purpose">2.1 Purpose</a></li>
- <li><a href="#Intended_Audience">2.2 Intended Audience</a></li>
- <li><a href="#Documentation_Conventions">2.3 Documentation Conventions</a></li>
- <li><a href="#Using_this_document">2.4 Using this Document</a></li>
+ <li><a href="#Purpose">Purpose</a></li>
+ <li><a href="#Intended_Audience">Intended Audience</a></li>
+ <li><a href="#Documentation_Conventions">Documentation Conventions</a></li>
+ <li><a href="#Using_this_document">Using This Document</a></li>
</ol></li>
- <li><a href="#Overview">3. Overview</a>
+ <li><a href="#Overview">Overview</a>
<ol>
- <li><a href="#Key_Feature">3.1 Key Features</a></li>
- <li><a href="#TM_in_VM">3.2 Thread Manager in VM</a></li>
- <li><a href="#Portability">3.3 Portability</a></li>
+ <li><a href="#Key_Feature">Key Features</a></li>
+ <li><a href="#TM_in_VM">Thread Manager in VM</a></li>
+ <li><a href="#Portability">Portability</a></li>
</ol></li>
- <li><a href="#Achitecture">4. Architecture</a>
+ <li><a href="#Achitecture">Architecture</a>
<ol>
- <li><a href="#Exported_Interfaces">4.1 Exported interfaces</a>
- <ul>
- <li><a href="#Native_Layer">4.1.1 Native Interface</a></li>
- <li><a href="#Java_interface">4.1.2 Java* Interface</a></li>
- </ul></li>
- <li><a href="#Data_Structures">4.2 Data structures</a></li>
- <li><a href="#Thread_Control_Structure">4.3 Thread control structures</a>
- <ul>
- <li><a href="#Native_Structure">4.3.1 Native Thread Structure</a></li>
- <li><a href="#Java_Structure">4.3.2 Java* Thread Structure</a></li>
- </ul></li>
- <li><a href="#Thread_Group">4.4 Thread Groups</a></li>
- <li><a href="#Synchronizer">4.5 Synchronizers</a></li>
- <li><a href="#Monitors">4.6 Monitors</a>
- <ul>
- <li><a href="#MonitorInflation">4.6.1 Inflation Technique</a></li>
- <li><a href="#Thin_monitors">4.6.2 Monitor Structure</a></li>
- <li><a href="#AcquireMonitor">4.6.3 Acquiring a Monitor</a></li>
- </ul></li>
+ <li><a href="#Exported_Interfaces">Exported interfaces</a>
+ <ol>
+ <li><a href="#Native_Layer">Native Interface</a></li>
+ <li><a href="#Java_interface">Java* Interface</a></li>
+ </ol></li>
+ <li><a href="#Data_Structures">Data Structures</a></li>
+ <li><a href="#Thread_Control_Structure">Thread Control Structures</a>
+ <ol>
+ <li><a href="#Native_Structure">Native Thread Structure</a></li>
+ <li><a href="#Java_Structure">Java* Thread Structure</a></li>
+ </ol></li>
+ <li><a href="#Thread_Group">Thread Groups</a></li>
+ <li><a href="#Synchronizer">Synchronizers</a></li>
+ <li><a href="#Monitors">Monitors</a>
+ <ol>
+ <li><a href="#MonitorInflation">Inflation Technique</a></li>
+ <li><a href="#Thin_monitors">Monitor Structure</a></li>
+ <li><a href="#AcquireMonitor">Acquiring a Monitor</a></li>
+ </ol></li>
</ol></li>
- <li><a href="#Usage_Scenarios">5. Usage scenarios</a>
+ <li><a href="#Usage_Scenarios">Usage Scenarios</a>
<ol>
- <li><a href="#Thread_lifecycle">5.1 Java* Thread Life Cycle</a></li>
- <li><a href="#Thread_suspension">5.2 Thread Suspension</a></li>
- <li><a href="#Stop-the-world_Suspension">5.3 Stop-the-world Thread Suspension</a></li>
- <li><a href="#Thread_locking">5.4 Thread Locking</a></li>
- <li><a href="#Monitor_scenarios">5.5 Monitor Enter and Exit</a></li>
+ <li><a href="#Thread_lifecycle">Java* Thread Life Cycle</a></li>
+ <li><a href="#Thread_suspension">Thread Suspension</a></li>
+ <li><a href="#Stop-the-world_Suspension">Stop-the-world Thread Suspension</a></li>
+ <li><a href="#Thread_locking">Thread Locking</a></li>
+ <li><a href="#Monitor_scenarios">Monitor Enter and Exit</a></li>
</ol></li>
- <li><a href="#References">6. References</a></li>
+ <li><a href="#References">References</a></li>
</ol>
<h1>
- <a id="RevisionHistory" name="RevisionHistory"></a>1. Revision History
+ <a id="RevisionHistory" name="RevisionHistory"></a>Revision History
</h1>
<table border="0" cellpadding="0" width="100%">
<tr>
@@ -106,11 +106,11 @@
</table>
<h1>
- <a id="About_This_Document" name="About_This_Document"></a>2. About
+ <a id="About_This_Document" name="About_This_Document"></a>About
This Document
</h1>
<h2>
- <a id="Purpose" name="Purpose"></a>2.1 Purpose
+ <a id="Purpose" name="Purpose"></a>Purpose
</h2>
<p>
This document introduces the thread manager component delivered as
@@ -120,7 +120,7 @@
organization of the thread management subsystem.
</p>
<h2>
- <a id="Intended_Audience" name="Intended_Audience"></a>2.2 Intended
+ <a id="Intended_Audience" name="Intended_Audience"></a>Intended
Audience
</h2>
<p>
@@ -132,15 +132,15 @@
</p>
<h2>
<a id="Documentation_Conventions"
- name="Documentation_Conventions"></a>2.3 Documentation Conventions
+ name="Documentation_Conventions"></a>Documentation Conventions
</h2>
<p>
This document uses the <a href="../../documentation/conventions.html">
unified conventions</a> for the DRL documentation kit.
</p>
<h2>
- <a id="Using_this_document" name="Using_this_document"></a>2.4 Using
- this Document
+ <a id="Using_this_document" name="Using_this_document"></a>Using
+ This Document
</h2>
<p>
Use this document to learn all about implementation specifics of the
@@ -173,7 +173,7 @@
<a href="#top">Back to Top</a>
</p>
<h1>
- <a id="Overview" name="Overview"></a>3. Overview
+ <a id="Overview" name="Overview"></a>Overview
</h1>
<p>
The thread manager (TM) is a library aimed to provide threading
@@ -228,7 +228,7 @@
<a href="#top">Back to Top</a>
</p>
<h2>
- <a id="Key_Feature" name="Key_Feature"></a>3.1 Key features
+ <a id="Key_Feature" name="Key_Feature"></a>Key Features
</h2>
<p>
The supplied thread manager has the following characteristics:
@@ -256,7 +256,7 @@
</li>
</ul>
<h2>
- <a id="TM_in_VM" name="TM_in_VM"></a>3.2 Thread Manager in VM
+ <a id="TM_in_VM" name="TM_in_VM"></a>Thread Manager in VM
</h2>
<p>
Figure 2 below demonstrates the interaction of the thread manager with
@@ -296,7 +296,7 @@
Figure 2: Thread Manager in VM Architecture
</p>
<h2>
- <a id="Portability" name="Portability"></a>3.3 Portability
+ <a id="Portability" name="Portability"></a>Portability
</h2>
<p>
The thread manager code is mostly platform-independent and relies on
@@ -317,7 +317,7 @@
<a href="#top">Back to Top</a>
</p>
<h1>
- <a id="Achitecture" name="Achitecture"></a>4. Architecture
+ <a id="Achitecture" name="Achitecture"></a>Architecture
</h1>
<p>
Subsequent sections describe the functional interfaces that the thread
@@ -325,8 +325,8 @@
data structures.
</p>
<h2>
- <a id="Exported_Interfaces" name="Exported_Interfaces"></a>4.1
- Exported interfaces
+ <a id="Exported_Interfaces" name="Exported_Interfaces"></a>
+ Exported Interfaces
</h2>
<p>
As indicated in the overview, the thread manager exports the native
@@ -335,7 +335,7 @@
upon external requests, as described in the subsequent sections.
</p>
<h3>
- <a id="Native_Layer" name="Native_Layer"></a>4.1.1 Native Interface
+ <a id="Native_Layer" name="Native_Layer"></a>Native Interface
</h3>
<p>
The native interface is inspired by the Harmony <code>hythread</code>
@@ -431,7 +431,7 @@
<a href="#top">Back to Top</a>
</p>
<h3>
- <a id="Java_interface" name="Java_interface"></a>4.1.2 Java<a
+ <a id="Java_interface" name="Java_interface"></a>Java<a
href="#*">*</a> Interface
</h3>
<p>
@@ -519,7 +519,7 @@
<a href="#Top">Back to Top</a>
</p>
<h2>
- <a id="Data_Structures" name="Data_Structures"></a>4.2 Data structures
+ <a id="Data_Structures" name="Data_Structures"></a>Data Structures
</h2>
<p>
The thread manager data structures are typically not exposed: external
@@ -531,7 +531,7 @@
</p>
<h2>
<a id="Thread_Control_Structure"
- name="Thread_Control_Structure"></a>4.3 Thread control structures
+ name="Thread_Control_Structure"></a>Thread Control Structures
</h2>
<p>
The thread manager requires each thread to be <em>registered</em>
@@ -580,7 +580,7 @@
handle.
</p>
<h3>
- <a id="Native_Structure" name="Native_Structure"></a>4.3.1 Native
+ <a id="Native_Structure" name="Native_Structure"></a>Native
Thread Structure
</h3>
<p>
@@ -596,7 +596,7 @@
</p>
<p class="notetext">
The actual content of a thread control structure is
- implementation-specific and is not exposed to other components.
+ implementation-specific and is not exposed to other components.
</p>
<p>
The following figure shows the thread control structure of a native
@@ -607,7 +607,7 @@
alt="Structure of a native thread not registered in TM" />
</p>
<p class="special">
- Figure 3: Native Thread
+ Figure 3: Native Thread
</p>
<p>
The following table lists the data fields making up the thread control
@@ -972,7 +972,7 @@
<a href="#Top">Back to Top</a>
</p>
<h3>
- <a id="Java_Structure" name="Java_Structure"></a>4.3.2 Java<a
+ <a id="Java_Structure" name="Java_Structure"></a>Java<a
href="#*">*</a> Thread Structure
</h3>
<p>
@@ -1164,7 +1164,7 @@
<a href="#Top">Back to Top</a>
</p>
<h2>
- <a id="Thread_Group" name="Thread_Group"></a>4.4 Thread Groups
+ <a id="Thread_Group" name="Thread_Group"></a>Thread Groups
</h2>
<p>
The thread manager enables co-existence of multiple groups of threads,
@@ -1192,7 +1192,7 @@
<a href="#Top">Back to Top</a>
</p>
<h2>
- <a id="Synchronizer" name="Synchronizer"></a>4.5 Synchronizers
+ <a id="Synchronizer" name="Synchronizer"></a>Synchronizers
</h2>
<p>
The thread manager synchronizers are functional modules used for
@@ -1267,7 +1267,7 @@
<a href="#Top">Back to Top</a>
</p>
<h2>
- <a id="Monitors" name="Monitors"></a>4.6 Monitors
+ <a id="Monitors" name="Monitors"></a>Monitors
</h2>
<p>
The current version of the thread manager implements Java<a
@@ -1277,8 +1277,8 @@
optimized for space consumption and single-threaded usage.
</p>
<h3>
- <a id="MonitorInflation" name="MonitorInflation"></a>4.6.1 Inflation
- technique
+ <a id="MonitorInflation" name="MonitorInflation"></a>Inflation
+ Technique
</h3>
<p>
Monitor inflation is implemented using a thin-fat lock technique [<a
@@ -1309,7 +1309,7 @@
href="#*">*</a> monitors space usage more efficient.
</p>
<h3>
- <a id="Thin_monitors" name="Thin_monitors"></a>4.6.2 Monitor Structure
+ <a id="Thin_monitors" name="Thin_monitors"></a>Monitor Structure
</h3>
<p>
The thin monitor is a synchronizer primitive that implements the lock
@@ -1401,7 +1401,7 @@
<a href="#Top">Back to Top</a>
</p>
<h3>
- <a id="AcquireMonitor" name="AcquireMonitor"></a>4.6.3 Acquiring a
+ <a id="AcquireMonitor" name="AcquireMonitor"></a>Acquiring a
Monitor
</h3>
<p>
@@ -1441,14 +1441,14 @@
<a href="#Top">Back to Top</a>
</p>
<h1>
- <a id="Usage_Scenarios" name="Usage_Scenarios"></a>5. Usage scenarios
+ <a id="Usage_Scenarios" name="Usage_Scenarios"></a>Usage Scenarios
</h1>
<p>
This section contains various scenarios of thread manipulation.
</p>
<h2>
- <a id="Thread_lifecycle" name="Thread_lifecycle"></a>5.1 Java<a
- href="#*">*</a> thread life cycle
+ <a id="Thread_lifecycle" name="Thread_lifecycle"></a>Java<a
+ href="#*">*</a> Thread Life Cycle
</h2>
<p>
The Java<a href="#*">*</a> thread creation procedure consists of the
@@ -1544,7 +1544,7 @@
<a href="#Top">Back to Top</a>
</p>
<h2>
- <a id="Thread_suspension" name="Thread_suspension"></a>5.2 Thread
+ <a id="Thread_suspension" name="Thread_suspension"></a>Thread
Suspension
</h2>
<p>
@@ -1572,7 +1572,7 @@
the current state of thread T2, the
<code>hythread_suspend(T2)</code> function activates one of the
following mechanisms:
- <ol>
+ <ul>
<li>
If thread T2 is currently running in a safe code region, the
<code>hythread_suspend(T2)</code> call immediately returns,
@@ -1584,7 +1584,7 @@
thread T2 reaches the beginning of a safe region or a safe
point.
</li>
- </ol>
+ </ul>
</li>
<li>
Thread T2 runs to the end of the safe region and gets blocked until
@@ -1663,7 +1663,7 @@
</p>
<h2>
<a id="Stop-the-world_Suspension"
- name="Stop-the-world_Suspension"></a>5.3 Stop-the-world Thread
+ name="Stop-the-world_Suspension"></a>Stop-the-world Thread
Suspension
</h2>
<p>
@@ -1695,7 +1695,7 @@
<a href="#Top">Back to Top</a>
</p>
<h2>
- <a id="Thread_locking" name="Thread_locking"></a>5.4 Thread Locking
+ <a id="Thread_locking" name="Thread_locking"></a>Thread Locking
</h2>
<p>
Locking with the thread manager can be done by means of a mutex or a
@@ -1730,8 +1730,8 @@
<a href="#Top">Back to Top</a>
</p>
<h2>
- <a id="Monitor_scenarios" name="Monitor_scenarios"></a>5.5 Monitor
- enter and exit
+ <a id="Monitor_scenarios" name="Monitor_scenarios"></a>Monitor
+ Enter and Exit
</h2>
<p>
Locking Java<a href="#*">*</a> monitors implies interaction between
@@ -1790,7 +1790,7 @@
<a href="#Top">Back to Top</a>
</p>
<h1>
- <a id="References" name="References"></a>6. References
+ <a id="References" name="References"></a>References
</h1>
<p>
This section lists the resources used in this document and other
Modified: harmony/standard/site/xdocs/subcomponents/drlvm/debugging_VM_and_JIT.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/debugging_VM_and_JIT.html?view=diff&rev=525159&r1=525158&r2=525159
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/debugging_VM_and_JIT.html (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/debugging_VM_and_JIT.html Tue Apr 3 07:10:50 2007
@@ -22,66 +22,77 @@
"text/html; charset=ISO-8859-1">
<title>Debugging DRL Virtual Machine and JIT Compiler </title>
</head>
-<body>
- <h1>
- <a name="top"></a>Debugging the DRL Virtual Machine and the JIT Compiler
- </h1>
+ <body>
+ <h1><a id="top" name="top"></a>Debugging the DRL Virtual Machine and the JIT Compiler</h1>
+<ol id="TOC">
+<li><a href="#About_This_Document">About This Document</a></li>
+<li><a href="#Debugging_VM">Debugging the Virtual Machine</a>
+ <ol>
+ <li><a href="#How_to_debug_VM">How to Debug the VM</a>
+ <ol>
+ <li><a href="#Basic_Debugging_Steps">Basic Debugging Steps</a></li>
+ <li><a href="#Attaching_the_Debugger">Attaching the Debugger to the Live Process</a></li>
+ </ol>
+ </li>
+ <li><a href="#Extended_Debug_VM">How to Get More of Your Debugging</a>
+ <ol>
+ <li><a href="#Configuration_of_Tracing">Configuration of Tracing</a></li>
+ <li><a href="#Native_Stack_Examination">Native Stack Examination</a></li>
+ <li><a href="#Stack_Examination">Java* Stack Examination</a></li>
+ <li><a href="#Setting_Breakpoints">Setting Smart Breakpoints</a></li>
+ <li><a href="#Handling_Threads">Handling Java* Threads as Native Threads</a></li>
+ <li><a href="#Debugging_Deadlocks">Debugging Deadlocks with the
+ <code>CriticalSection</code> Synchronization Primitive</a></li>
+ <li><a href="#Getting_a_Class_Name">Getting a Class Name for an Object</a></li>
+ </ol>
+ </li>
+ </ol>
+</li>
+<li><a href="#Debugging_JIT">Debugging the Jitrino.JET Baseline Compiler</a>
+ <ol>
+ <li><a href="#Enable_Tracing">How to Enable Tracing in Jitrino.JET</a></li>
+ <li><a href="#Config_Trace_Logging">How to Configure Trace Logging</a>
+ <ol>
+ <li><a href="#Compilation_Results_Tracing">Group 1: Compilation Results Tracing</a></li>
+ <li><a href="#Run-time_Execution_Tracing">Group 2: Run-time Execution Tracing</a></li>
+ </ol>
+ </li>
+ <li><a href="#Extend_Trace_JIT">How to Get More of Your Tracing</a>
+ <ol>
+ <li><a href="#Tracing_Example">Tracing Example</a></li>
+ </ol>
+ </li>
+ </ol>
+</li>
+</ol>
+ <h1><a id="About_This_Document" name="About_This_Document"></a>About This Document</h1>
<p>
This document gives practical instructions on how to debug the DRL virtual machine
and its baseline just-in-time compiler Jitrino.JET. For a definition of components
and details on their internal structure, consult the <a href="../../subcomponents/drlvm/developers_guide.html">
- DRL Virtual Machine Developer’s Guide</a> supplied with the DRLVM image.
+ DRL Virtual Machine Developer’s Guide</a> supplied with the DRLVM image.
</p>
<p>
The document includes two groups of debugging tips, one for VM tips, and the other
for JIT compiler tips, as shown below.
</p>
- <p class="TOCHeading">
- <a href="#Debugging_VM">Debugging the Virtual Machine</a>
- </p>
-<p class="TOC">
- <a href="#How_to_debug_VM">How to debug the VM?</a>
- </p>
-<p class="TOC">
- <a href="#Extended_Debug_VM">How to get more of your debugging?</a>
- </p>
-<p class="TOCHeading">
- <a href="#Debugging_JIT">Debugging the Jitrino.JET Baseline Compiler</a>
- </p>
-<p class="TOC">
- <a href="#Enable_Tracing">How to enable tracing in Jitrino.JET?</a>
- </p>
-<p class="TOC">
- <a href="#Config_Trace_Logging">How to configure trace logging?</a>
- </p>
-<p class="TOC">
- <a href="#Extend_Trace_JIT">How to get more of your tracing?</a>
- </p>
- <p><a href="#top">Back to top</a>
- </p>
- <h1>
- <a name="Debugging_VM">Debugging the Virtual Machine</a>
- </h1>
- <p>
+ <p><a href="#top">Back to top</a></p>
+ <h1><a id="Debugging_VM" name="Debugging_VM"></a>Debugging the Virtual Machine</h1>
+ <p>
This section gives an insight into debugging the DRL virtual machine version 1.0
and provides tips on resolving non-standard debugging issues.
</p>
- <h2>
- <a name="How_to_debug_VM">How to debug the VM?</a>
- </h2>
+ <p><a href="#top">Back to top</a></p>
+ <h2><a id="How_to_debug_VM" name="How_to_debug_VM"></a>How to Debug the VM</h2>
<p>
This section gives instructions on different scenarios of debugging the VM source
code.
</p>
- <h3>
- Basic Debugging Steps
- </h3>
- <p>
- For ordinary tests, start the ij executable with the debugger enabled, as follows:
- </p>
- <p class="class">
- On Windows<a href="#*">*</a></p>
- <ol>
+ <h3><a id="Basic_Debugging_Steps" name="Basic_Debugging_Steps"></a>Basic Debugging Steps</h3>
+ <p>For ordinary tests, start the ij executable with the debugger enabled, as follows:</p>
+ <dl>
+ <dt>On Windows<a href="#*">*</a></dt>
+ <dd><ol>
<li>Start Microsoft Visual Studio<a href="#*">*</a> and open the solution file <code>
vm\build\vm.sln</code>. </li>
<li>Open the source code that you need to debug, set breakpoints and perform all other
@@ -93,10 +104,9 @@
</li>
<li>Start debugging via the menu <strong>Debug</strong> > <strong>Start</strong>,
click <strong>NO</strong> in the popup dialog offering to build the project. </li>
- </ol>
- <p class="class">
- On Linux<a href="#*">*</a></p>
- <ol>
+ </ol></dd>
+ <dt>On Linux<a href="#*">*</a></dt>
+ <dd><ol>
<li>Set up the <code>LD_LIBRARY_PATH</code> to point to the <code>deploy/jre/bin</code>
directory. Change the working directory to the location of the VM executable and
run:
@@ -110,61 +120,41 @@
run <your_params>
</pre>
</li>
- </ol>
- <p>
- <a href="#top">Back to top</a>
- </p>
- <h3>
- Attaching the Debugger to the Live Process
- </h3>
- <p>
- To attach to the running VM process, do the following:
- </p>
- <p class="class">
- On Windows<a href="#*">*</a></p>
- <ol>
+ </ol></dd></dl>
+
+ <h3><a id="Attaching_the_Debugger" name="Attaching_the_Debugger"></a>Attaching the Debugger to the Live Process</h3>
+ <p>
+ To attach to the running VM process, do the following:</p>
+ <dl><dt>On Windows<a href="#*">*</a></dt>
+ <dd><ol>
<li>Start Visual Studio<a href="#*">*</a> . </li>
<li>Go <strong>Debug</strong> > <strong>Processes</strong>. </li>
<li>Select the VM process and click <strong>Attach</strong>.<br>
If you built the VM in the debug mode, the <strong>Microsoft Debug Runtime</strong>
window appears. Click the <strong>Debug</strong> button to go to the crash point.
</li>
- </ol>
- <p class="class">
- On Linux<a href="#*">*</a></p>
- <p>
+ </ol></dd>
+ <dt>On Linux<a href="#*">*</a></dt>
+ <dd>
Run:
- </p>
- <pre>
-gdb –p <PID of ij>
-</pre>
- <p>
+<pre>gdb –p <PID of ij></pre>
+
If the VM crashed during execution, use the core dump to analyze the crash:
- </p>
- <pre>
-gdb ij core
-</pre>
- <p>
- <a href="#top">Back to top</a>
- </p>
- <h2>
- <a name="Extended_Debug_VM">How to get more from your debugging?</a>
- </h2>
+<pre>gdb ij core</pre>
+</dd></dl>
+ <p><a href="#top">Back to top</a></p>
+ <h2><a id="Extended_Debug_VM" name="Extended_Debug_VM"></a>How to Get More from Your Debugging</h2>
<p>
This section includes some tips on optimizing the debug process and getting more
debug information.
</p>
- <h3>
- Configuration of tracing
- </h3>
+ <h3><a id="Configuration_of_Tracing" name="Configuration_of_Tracing"></a>Configuration of Tracing</h3>
<p>
Consult the <a href="../../subcomponents/drlvm/getting_started.html">Getting Started
- guide</a> delivered with DRLVM bundle for information on VM standard and non-standard
+ guide</a> delivered with DRLVM bundle for information on VM standard and non-standard
configuration options. Tracing-related options might be useful for debugging purposes.
</p>
- <h3>
- Native stack examination
- </h3>
+ <h3><a id="Native_Stack_Examination" name="Native_Stack_Examination"></a>Native Stack Examination</h3>
<p>
The debugger might draw the stack incorrectly when the JIT or native stubs are involved.
To avoid this, set esp as the memory location and 4-byte integer values as the output
@@ -195,79 +185,66 @@
call stack in the <strong>Call Stack</strong> window. If you have found a wrong
call site, repeat the instruction from step 2. </li>
</ol>
- <p>
- <a href="#top">Back to top</a>
- </p>
- <h3>
- Java<a href="#*">*</a> stack examination
- </h3>
- <p class="class">
- On Windows<a href="#*">*</a></p>
- <p>
+
+ <h3><a id="Stack_Examination" name="Stack_Examination"></a>Java<a href="#*">*</a> Stack Examination</h3>
+ <dl><dt>On Windows<a href="#*">*</a></dt>
+ <dd>
Running the VM in the interpreter mode, you can get Java<a href="#*">*</a> methods
stack trace almost at any point of execution. For that, break the execution of the
VM and select the <strong>Interpreter</strong> frame in the Visual Studio<a href="#*">*</a>
<strong>Call Stack</strong> window. Then, in the watch window, add the watch <code>stack_dump()</code>.
The stack dump appears in VM output window. Running the VM in the JIT mode, use
the <code>st_print()</code> function for the same purpose.
- </p>
- <p class="class">
- On Linux<a href="#*">*</a></p>
- <p>
+ </dd>
+ <dt>On Linux<a href="#*">*</a></dt>
+ <dd>
Use the <code>gdb</code> command print and specify the <code>stack_dump</code> or
<code>st_print</code> in the interpreter or the JIT compiler mode respectively.
- </p>
- <h3>
- Setting smart breakpoints
- </h3>
- <p class="class">
- On Windows<a href="#*">*</a> / IA-32</p>
- <p>
+ </dd></dl>
+
+ <h3><a id="Setting_Breakpoints" name="Setting_Breakpoints"></a>Setting Smart Breakpoints</h3>
+ <dl><dt>On Windows<a href="#*">*</a> / IA-32</dt>
+ <dd>
Place breakpoints in source code by inserting calls to the <code>_CrtDbgBreak()</code>
function. Placing the call inside a condition calls the function only for the specified
case you need to debug. Analogously, you can use the Windows<a href="#*">*</a> API
function <code>DebugBreak()</code> or print <code>INT 3</code>.
- </p>
+
<p class="note">
Note</p>
<p class="notetext">
- This requires recompiling the VM.</p>
- <p class="class">
- On Linux<a href="#*">*</a></p>
- <p>
+ This requires recompiling the VM.</p></dd>
+ <dt>
+ On Linux<a href="#*">*</a></dt>
+ <dd>
Run the following:
- </p>
- <pre>
-__asm {int 3}
-</pre>
- <p>
- <a href="#top">Back to top</a>
- </p>
- <h3>
- Handling Java<a href="#*">*</a> threads as native threads
- </h3>
+<pre>__asm {int 3}</pre>
+</dd></dl>
+
+ <h3><a id="Handling_Threads" name="Handling_Threads"></a>
+ Handling Java<a href="#*">*</a> Threads as Native Threads</h3>
<p>
DRL VM has 1:1 mapping between native threads visible in the debugger and Java<a
- href="#*">*</a> threads.<br>
+ href="#*">*</a> threads.<br \>
To work with Java<a href="#*">*</a> threads individually, freeze the threads you
do not need with the help of the debugger, and continue execution of other threads.
</p>
- <h3>
- Debugging deadlocks with the CriticalSection synchronization primitive
+ <h3><a id="Debugging_Deadlocks" name="Debugging_Deadlocks"></a>
+ Debugging Deadlocks with the <code>CriticalSection</code> Synchronization Primitive
</h3>
<p>
The <code>CriticalSection</code> primitive is a common cause of deadlocks. If the
code has stopped at a critical section, you can try to find the thread that owns
this primitive.
</p>
- <p class="class">
- On Windows<a href="#*">*</a></p>
- <p>
+ <dl>
+ <dt>On Windows<a href="#*">*</a></dt>
+ <dd>
The file <code>WinNT.H</code> located in <code><PlatformSDK>\Include</code>
contains the definition for the structure <code>_RTL_CRITICAL_SECTION</code>, which
contains the description of the CriticalSection primitive. You can get the owning
thread for the CriticalSection primitive in a number of ways, as indicated below.
- </p>
+
<p>
<strong>Lookup in Memory</strong></p>
<p>
@@ -286,7 +263,7 @@
<p class="notetext">
Visual Studio<a href="#*">*</a> displays thread IDs in decimal representation.</p>
<p>
- <strong>In the watch window</strong></p>
+ <strong>In the Watch Window</strong></p>
<p>
In the watch window of Visual Studio<a href="#*">*</a>, insert the following:
</p>
@@ -295,24 +272,19 @@
</pre>
<p>
Where <code><cs-ptr></code> is the address of your critical section
- </p>
- <p class="class">
- On Linux<a href="#*">*</a></p>
- <p>
+ </p> </dd>
+ <dt>On Linux<a href="#*">*</a></dt>
+ <dd>
The file <code>/usr/include/bits/pthreadtypes.h</code> contains the description
of the <code>pthread_mutex_t</code> type. To get the ID of the thread owning the
<code>CriticalSection</code> primitive, in <code>gdb</code> execute:
- </p>
- <pre>
-x/4w <address of your mutex primitive>
-</pre>
+<pre>x/4w <address of your mutex primitive></pre>
<p>
The third word in the output contains the owning thread descriptor you are looking
for.
- </p>
- <h3>
- Getting a class name for an object
- </h3>
+ </p></dd></dl>
+ <h3><a id="Getting_a_Class_Name" name="Getting_a_Class_Name"></a>
+ Getting a Class Name for an Object</h3>
<p>
You can often need to find out the class name for a Java<a href="#*">*</a> object
used in VM code. For example, you may need to get the class name for an object of
@@ -333,15 +305,16 @@
<a href="#top">Back to top</a>
</p>
<h1>
- <a name="Debugging_JIT"></a>Debugging the Jitrino.JET Baseline Compiler
+ <a id="Debugging_JIT" name="Debugging_JIT"></a>Debugging the Jitrino.JET Baseline Compiler
</h1>
<p>
To use debugging and tracing in Jitrino.JET, use the debug build or the release
build with the <code>JET_PROTO</code> macro defined. See the file <code>jdefs.h</code>
for a definition of the available flags.
</p>
+ <p><a href="#top">Back to top</a></p>
<h2>
- <a name="Enable_Tracing"></a>How to enable tracing in Jitrino.JET?
+ <a id="Enable_Tracing" name="Enable_Tracing"></a>How to Enable Tracing in Jitrino.JET
</h2>
<p>
Currently, Jitrino.JET provides no interface or command line to control tracing
@@ -351,8 +324,9 @@
compiled, and the instance variable <code>m_fname</code> contains its fully qualified
name with no signature. Obtain these options through a call to <code>Compiler::m_infoBlock.get_flags()</code>.
</p>
+ <p><a href="#top">Back to top</a></p>
<h2>
- <a name="Config_Trace_Logging"></a>How to configure trace logging?
+ <a id="Config_Trace_Logging" name="Config_Trace_Logging"></a>How to Configure Trace Logging
</h2>
<p>
Tracing flags control compilation results output and trace run-time execution, as
@@ -360,9 +334,8 @@
the <code>ij</code> executable starts: compilation results are in <code>jet.log</code>,
and run-time output is in <code>jet.rt.log</code>.
</p>
- <h3>
- Group 1: Compilation Results Tracing
- </h3>
+ <h3><a id="Compilation_Results_Tracing" name="Compilation_Results_Tracing"></a>
+ Group 1: Compilation Results Tracing</h3>
<p>
The following flags control tracing compilation of a method:
</p>
@@ -412,12 +385,9 @@
</p>
</li>
</ul>
- <p>
- <a href="#top">Back to top</a>
- </p>
- <h3>
- Group 2: Run-time Execution tracing
- </h3>
+
+ <h3><a id="Run-time_Execution_Tracing" name="Run-time_Execution_Tracing"></a>
+ Group 2: Run-time Execution Tracing</h3>
<p>
The following flags trace run-time life of the method:
</p>
@@ -458,11 +428,8 @@
The output goes to jet.log, with the address (both native and PC) where the event
happens, and some other info.
</p>
- <p>
- <a href="#top">Back to top</a>
- </p>
- <h2>
- <a name="Extend_Trace_JIT">How to get more from your tracing?</a>
+ <p><a href="#top">Back to top</a></p>
+ <h2><a id="Extend_Trace_JIT" name="Extend_Trace_JIT">How to Get More from Your Tracing</a>
</h2>
<p>
To identify one or more problematic methods with another stable JIT compiler, use
@@ -488,10 +455,7 @@
to break execution at the specified bytecode instruction or at the entry point of
the specified method.
</p>
- <p>
- <a href="#top">Back to top</a>
- </p>
- <h3>
+ <h3><a id="Tracing_Example" name="Tracing_Example"></a>
Tracing Example
</h3>
<p>
@@ -716,8 +680,9 @@
<p>
<a name="*"></a>* Other brands and names are the property of their respective owners.
</p>
-</body>
+ </body>
</html>
+
Modified: harmony/standard/site/xdocs/subcomponents/drlvm/emguide.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/emguide.xml?view=diff&rev=525159&r1=525158&r2=525159
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/emguide.xml (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/emguide.xml Tue Apr 3 07:10:50 2007
@@ -24,16 +24,22 @@
<body>
<section name="Guide to Execution Manager Configuration">
-<subsection name="Contents">
-<ol>
-<li><a href="#1. What is EM?">What is EM?</a></li>
-<li><a href="#2. EM Configuration File">EM Configuration File</a></li>
-<li><a href="#3. EM Tracing Options">EM tracing options</a></li>
-<li><a href="#4. More EM Configuration Samples">More EM Configuration Samples</a></li>
-</ol>
-</subsection>
+ <ol id="TOC">
+ <li>
+ <a href="#What is EM?">What is EM?</a>
+ </li>
+ <li>
+ <a href="#EM Configuration File">EM Configuration File</a>
+ </li>
+ <li>
+ <a href="#EM Tracing Options">EM Tracing Options</a>
+ </li>
+ <li>
+ <a href="#More EM Configuration Samples">More EM Configuration Samples</a>
+ </li>
+ </ol>
-<subsection name="1. What is EM?">
+<subsection name="What is EM?">
<p>
Execution Manager (EM) is a component in DRLVM that controls
profile collection and recompilation processes.
@@ -41,7 +47,7 @@
For detailed information on EM, see the <a href="EM.html">Execution Manager Component Description</a>.
</p>
</subsection>
-<subsection name="2. EM Configuration File">
+<subsection name="EM Configuration File">
<p>
The set of JIT compilers and profile collectors used at run time and their
relations is stored in the <i>EM configuration file</i>.
@@ -234,7 +240,7 @@
recompilation with the next JIT in the current chain.
</p>
</subsection>
-<subsection name="3. EM Tracing Options">
+<subsection name="EM Tracing Options">
<p>
Use the following command-line options to trace EM events:</p>
<ul>
@@ -277,7 +283,7 @@
...
</pre>
</subsection>
-<subsection name="4. More EM Configuration Samples">
+<subsection name="More EM Configuration Samples">
<p>
DRLVM has several EM configurations supplied in the following files:
<code>client.emconf</code> (the default), <code>opt.emconf</code>, <code>jet.emconf</code>,
Modified: harmony/standard/site/xdocs/subcomponents/drlvm/encoder_library.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/encoder_library.xml?view=diff&rev=525159&r1=525158&r2=525159
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/encoder_library.xml (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/encoder_library.xml Tue Apr 3 07:10:50 2007
@@ -27,44 +27,26 @@
<body>
<section name="Encoder Library Description for IA-32/Intel64">
- <subsection name="Contents">
- <ol>
- <li>
- <a href="#1. Revision History">Revision History</a>
- </li>
- <li><a href="#2. About this document">About
- this Document</a> </li>
-
- <li>
- <a href="#3. Overview">Overview</a>
- </li>
-
- <li>
- <a href="#4. Goals and Targets">Goals and Targets</a>
- </li>
-
- <li>
- <a href="#5. Structure">Structure</a>
- </li>
- <li>
- <a href="#6. How It Works">How It Works</a></li>
-
- <ul>
- <li><a href="#6.1 Usage Model">6.1 Usage Model</a></li>
- <li><a href="#6.2 Under the Hood">6.2 Under the
- Hood</a></li>
- <ul>
- <li><a href="#6.2.1 Fast Opcode Lookup">6.2.1 Fast
- Opcode Lookup</a>
- </li>
- <li><a href="#6.2.2 Fast Code Generation">6.2.2 Fast
- Code Generation</a></li>
- </ul>
- </ul>
- </ol>
- </subsection>
+ <ol id="TOC">
+ <li><a href="#Revision History">Revision History</a></li>
+ <li><a href="#About this document">About This Document</a></li>
+ <li><a href="#Overview">Overview</a></li>
+ <li><a href="#Goals and Targets">Goals and Targets</a></li>
+ <li><a href="#Structure">Structure</a></li>
+ <li><a href="#How It Works">How It Works</a>
+ <ol>
+ <li><a href="#Usage Model">Usage Model</a></li>
+ <li><a href="#Under the Hood">Under the Hood</a>
+ <ol>
+ <li><a href="#Fast Opcode Lookup">Fast Opcode Lookup</a></li>
+ <li><a href="#Fast Code Generation">Fast Code Generation</a></li>
+ </ol>
+ </li>
+ </ol>
+ </li>
+ </ol>
- <subsection name="1. Revision History">
+ <subsection name="Revision History">
<table>
<tr>
@@ -88,7 +70,7 @@
</table>
</subsection>
- <subsection name="2. About this Document">
+ <subsection name="About This Document">
<p>
This document introduces the encoder library component
delivered as a part of the DRL (Dynamic Runtime Layer)
@@ -98,7 +80,7 @@
</p>
</subsection>
- <subsection name="3. Overview">
+ <subsection name="Overview">
<p>
The encoder library is a DRLVM component for code
generation, or encoding. This library is separate, static and
@@ -126,7 +108,7 @@
</ul>
</subsection>
- <subsection name="4. Goals and Targets">
+ <subsection name="Goals and Targets">
<p>The encoder library meets the following requirements:</p>
@@ -151,7 +133,7 @@
<p class="notetext">
The encoder library provides a
simple and generic interface. Clients with special
- needs should use <a href="#6. How It Works">adapters</a>,
+ needs should use <a href="#How It Works">adapters</a>,
which provide a handy and convenient interface and then
translate the data into the generic interface.
</p>
@@ -160,7 +142,7 @@
</subsection>
- <subsection name="5. Structure">
+ <subsection name="Structure">
<p>The encoder library includes the following modules:</p>
@@ -327,11 +309,11 @@
</tr>
</table>
</subsection>
- <subsection name="6. How It Works">
+ <subsection name="How It Works">
- <h3><a name="6.1 Usage Model"><b>6.1 Usage Model</b></a></h3>
+ <h3><a name="Usage Model"><b>Usage Model</b></a></h3>
<p>
The base encoding interface
<code>EncoderBase::encode()</code> is a common generic
@@ -384,7 +366,7 @@
<code>vm/vmcore/include/jvmti_dasm.h</code>.
</p>
- <h3><a name="6.2 Under the Hood"><b>6.2 Under the Hood</b></a></h3>
+ <h3><a name="Under the Hood"><b>Under the Hood</b></a></h3>
<p>
The engine gets its input as an operation and a set of
@@ -404,14 +386,14 @@
table plain and elementary. At run time, before the first
usage, a special version of data is pre-compiled, which
requires fewer manipulations. The pre-compiled version provides
- the <a href="#6.2.1 Fast Opcode Lookup">fast opcode lookup</a> and
- the <a href="#6.2.2 Fast Code Generation">
+ the <a href="#Fast Opcode Lookup">fast opcode lookup</a> and
+ the <a href="#Fast Code Generation">
fast code generation</a>.
</p>
<dl>
<dt>
- <a name="6.2.1 Fast Opcode Lookup">6.2.1 Fast Opcode Lookup</a>
+ <a name="Fast Opcode Lookup">Fast Opcode Lookup</a>
</dt>
</dl>
@@ -433,7 +415,7 @@
<dl>
<dt>
- <a name="6.2.2 Fast Code Generation">6.2.2 Fast Code
+ <a name="Fast Code Generation">Fast Code
Generation</a>
</dt>
</dl>