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/01/25 16:35:05 UTC
svn commit: r499820 - in /harmony/standard/site:
docs/subcomponents/drlvm/JIT.html docs/subcomponents/drlvm/JIT_PMF.html
xdocs/subcomponents/drlvm/Jitrino.html
xdocs/subcomponents/drlvm/Jitrino_PMF.html
Author: nadinem
Date: Thu Jan 25 07:35:04 2007
New Revision: 499820
URL: http://svn.apache.org/viewvc?view=rev&rev=499820
Log:
resolve HARMONY-3055
Modified:
harmony/standard/site/docs/subcomponents/drlvm/JIT.html
harmony/standard/site/docs/subcomponents/drlvm/JIT_PMF.html
harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html
harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino_PMF.html
Modified: harmony/standard/site/docs/subcomponents/drlvm/JIT.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/JIT.html?view=diff&rev=499820&r1=499819&r2=499820
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/JIT.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/JIT.html Thu Jan 25 07:35:04 2007
@@ -463,7 +463,7 @@
machine using a combination of the native stack and registers.
</li>
<li>
- <a href="#Architecture">Jitrino.OPT</a> optimizing compiler can
+ <a href="#OPT_Architecture">Jitrino.OPT</a> optimizing compiler can
performs bytecode compilation with a variety of optimizations. The
compiler features two types of code <a href="#IR">intermediate
representation</a> (IR): platform-independent high-level IR (HIR)
@@ -535,7 +535,7 @@
</h2>
<p>
Jitrino compilers provide means to compile and optimize code
- distributed for Java<a href="#*#*">*</a> run-time environments and to
+ distributed for Java<a href="#*">*</a> run-time environments and to
adapt it to various hardware architectures. Figure 1 demonstrates the
architecture of the compilers and their interaction with the <a
href="developers_guide.html">virtual machine</a>.
@@ -577,7 +577,7 @@
<p>
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
+ 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>
@@ -653,7 +653,7 @@
VM properties. Understanding pipeline configuration rules is required
for using the Jitrino command-line interface and effectively
exercising the Jitrino logging system. For details on PMF internals,
- refer to the <a href="Jitrino_PMF.html">PMF Detailed Description</a>.
+ refer to the <a href="JIT_PMF.html">PMF Detailed Description</a>.
</p>
<p class="backtotop">
<a href="#top">Back to Top</a>
@@ -2014,7 +2014,7 @@
counters and time measurement, use the following command syntax:
</p>
<pre>
--Djit.<JIT>.arg.time=on
+-XDjit.<JIT>.arg.time=on
</pre>
<p class="note">
Note
@@ -2142,7 +2142,7 @@
The general syntax of the logging command follows PMF rules:
</p>
<pre>
--Djit.<JIT>.<pipeline>.arg.<path>.log=<list of stream names>
+-XDjit.<JIT>.<pipeline>.arg.<path>.log=<list of stream names>
</pre>
<p>
In this command syntax, <code><path></code> represents the set
@@ -2156,13 +2156,13 @@
To enable compilation protocols for all pipelines of all JITs, type
</p>
<pre class="exampletext">
--Djit.arg.log=info
+-XDjit.arg.log=info
</pre>
<p class="exampletext">
To dump compile-time diagnostic together with IR dumps, type
</p>
<pre class="exampletext">
--Djit.arg.log=ct,irdump
+-XDjit.arg.log=ct,irdump
</pre>
<h3>
5.3.1 CFG Visualization
@@ -2183,11 +2183,11 @@
To enable dumping .dot files, use the following command:
</p>
<pre>
--Djit.arg.log=dotdump
+-XDjit.arg.log=dotdump
</pre>
<p>
For more details on the Jitrino logging system, refer to the
- corresponding section in the <a href="PMF.html">PMF</a> description.
+ corresponding section in the <a href="JIT_PMF.html">PMF</a> description.
</p>
<p class="backtotop">
<a href="#top">Back to Top</a>
Modified: harmony/standard/site/docs/subcomponents/drlvm/JIT_PMF.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/JIT_PMF.html?view=diff&rev=499820&r1=499819&r2=499820
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/JIT_PMF.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/JIT_PMF.html Thu Jan 25 07:35:04 2007
@@ -344,7 +344,7 @@
<p>The document contains the detailed description of the
Jitrino pipeline management framework (PMF). For a high-level
- PMF overview, refer to the <a href="#Jitrino.html">Jitrino
+ PMF overview, refer to the <a href="JIT.html">Jitrino
document</a>.</p>
<h2><a id="Key_Elements"
@@ -476,7 +476,7 @@
</dd>
</dl>
- <p style="text-align: center"><img src="images/Pipeline.PNG"
+ <p style="text-align: center"><img src="images/Pipeline.png"
alt="package" /></p>
<p class="special">Figure 1: The Role of Pipelines in the JIT
@@ -582,14 +582,14 @@
<p>The general form of the JIT command is the following:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.<<b>parameter</b>>=<<b>value</b>>
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.<<b>parameter</b>>=<<b>value</b>>
</pre>
<p>Where</p>
<ul>
<li>
- <code>-Djit.</code> is the mandatory prefix enabling
+ <code>-XDjit.</code> is the mandatory prefix enabling
JIT commands selection from VM commands.
<p class="note">Note</p>
@@ -606,7 +606,7 @@
<p class="note">Note</p>
<p class="notetext">JITs are created by
- <a href="#EM.html">Execution Manager</a> (EM) using
+ <a href="EM.html">Execution Manager</a> (EM) using
information from the command line and/or
<a href="http://incubator.apache.org/harmony/subcomponents/drlvm/emguide.html">
<code>execution manager configuration</code>
@@ -658,13 +658,13 @@
a <i>command file</i> and read this file with a special <i>read
command</i>:</p>
<pre>
--Djit.read=<<b>command filename</b>>
+-XDjit.read=<<b>command filename</b>>
</pre>
<p class="note">Note</p>
<p class="notetext">Write commands in the command file without
- the prefix <code>-Djit</code>. The <code>read</code> command
+ the prefix <code>-XDjit</code>. The <code>read</code> command
itself can be used in the command file. The command file can
contain empty lines and comment lines starting with
<code>#</code> or <code>//</code>.</p>
@@ -693,7 +693,7 @@
non-terminal node of the tree is called a <i>path</i> and
defined by the following <i>path definition</i> command:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.path.<<b>name</b>>=<<b>child1</b>>,<<b>child2</b>>,...
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.path.<<b>name</b>>=<<b>child1</b>>,<<b>child2</b>>,...
</pre>
<p>The given command introduces a node with the specified name
@@ -717,9 +717,9 @@
and <code><b>a</b></code>, <code><b>b</b></code> and
<code><b>c</b></code> are the action names.</p>
<pre>
--Djit.OPT.path=M,N
--Djit.OPT.path.M=a
--Djit.OPT.path.N=b,c
+-XDjit.OPT.path=M,N
+-XDjit.OPT.path.M=a
+-XDjit.OPT.path.N=b,c
</pre>
<p class="exampletext">The given commands describe the simple
@@ -777,7 +777,7 @@
<p>To define a filter, use the following command format:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.filter=<<b>class</b>>.<<b>method</b>><<b>signature</b>>
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.filter=<<b>class</b>>.<<b>method</b>><<b>signature</b>>
</pre>
<p>Where</p>
@@ -812,7 +812,7 @@
<p class="example">Example</p>
<pre>
--Djit.OPT.p.filter=java/lang/Thread.check
+-XDjit.OPT.p.filter=java/lang/Thread.check
</pre>
<p class="exampletext">The following methods can match the
@@ -830,12 +830,12 @@
<p class="example">Example</p>
<pre>
--Djit.OPT.path=M,N
--Djit.OPT.path.M=a
--Djit.OPT.path.N=b,c
--Djit.OPT.p.path=M,N,O
--Djit.OPT.p.path.O=a
--Djit.OPT.p.filter=java/lang/Thread.check
+-XDjit.OPT.path=M,N
+-XDjit.OPT.path.M=a
+-XDjit.OPT.path.N=b,c
+-XDjit.OPT.p.path=M,N,O
+-XDjit.OPT.p.path.O=a
+-XDjit.OPT.p.filter=java/lang/Thread.check
</pre>
<p class="exampletext">The commands above are associated with
@@ -873,7 +873,7 @@
parameters passing convention. The parameter definition command
pattern is the following:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.<<b>param</b>>=<<b>value</b>>
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.<<b>param</b>>=<<b>value</b>>
</pre>
<p>Where</p>
@@ -905,7 +905,7 @@
<p class="example">Example</p>
<pre>
--Djit.OPT.p.arg.a.verify=1
+-XDjit.OPT.p.arg.a.verify=1
</pre>
<p class="exampletext">The given command sets the
@@ -930,7 +930,7 @@
<tr>
<td class="TableCell">
- <code>-Djit.OPT.p.arg.N.b.verify=2</code></td>
+ <code>-XDjit.OPT.p.arg.N.b.verify=2</code></td>
<td class="TableCell">
<center>
@@ -948,7 +948,7 @@
<tr>
<td class="TableCell">
- <code>-Djit.OPT.p.arg.N.verify=2</code></td>
+ <code>-XDjit.OPT.p.arg.N.verify=2</code></td>
<td class="TableCell">
<center>
@@ -963,7 +963,7 @@
<tr>
<td class="TableCell">
- <code>-Djit.OPT.p.arg.verify=2</code></td>
+ <code>-XDjit.OPT.p.arg.verify=2</code></td>
<td class="TableCell"><code><<b>full
name</b>></code></td>
@@ -977,7 +977,7 @@
<tr>
<td class="TableCell">
- <code>-Djit.OPT.arg.N.verify=2</code></td>
+ <code>-XDjit.OPT.arg.N.verify=2</code></td>
<td class="TableCell">
<code><<b>pipeline</b>></code></td>
@@ -993,8 +993,8 @@
<p>The special form of argument definition commands controls
the pipeline construction process:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>=on
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>=off
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>=on
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>=off
</pre>
<p class="note">Note</p>
@@ -1014,7 +1014,7 @@
<p class="exampletext">To exclude action <code><b>b</b></code>
from the pipeline, apply the following command:</p>
<pre>
--Djit.OPT.p.arg.N.b=off
+-XDjit.OPT.p.arg.N.b=off
</pre>
<p>To enable/disable nodes directly in the path definition
@@ -1064,7 +1064,7 @@
enabled, <code>c2</code> is disabled and <code>c3</code> is
enabled and mandatory:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.path.<<b>name</b>>=c1+,c2-,c3!
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.path.<<b>name</b>>=c1+,c2-,c3!
</pre>
<p>If you try to disable any mandatory node with the
@@ -1079,7 +1079,7 @@
pipeline actions. The VM property mechanism fully controls the
system.</p>
- <h2><a id="Stream_Definition"
+ <h2><a
name="Defining_Streams"></a>5.1 Defining Streams</h2>
<p>A set of <i>log streams</i> is used for logging in Jitrino.
@@ -1167,7 +1167,7 @@
<p>To enable outputting log information to a stream, enter a
command of the following syntax:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log=<<b>stream1</b>>,<<b>stream2</b>>,...
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log=<<b>stream1</b>>,<<b>stream2</b>>,...
</pre>
<p>The left part of the command specifies the name of the JIT
@@ -1197,8 +1197,8 @@
<code><b>N.b</b></code> and <code><b>N.c</b></code> by the same
name. The streams can be assigned to different files.</p>
<pre>
--Djit.OPT.p.arg.N.b.log=ct
--Djit.OPT.p.arg.N.c.log=ct
+-XDjit.OPT.p.arg.N.b.log=ct
+-XDjit.OPT.p.arg.N.c.log=ct
</pre>
<p class="backtotop"><a href="#top">Back to Top</a></p>
@@ -1210,7 +1210,7 @@
<p>To assign a stream to a file, use the following command
syntax:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.file=<<b>filename mask</b>>
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.file=<<b>filename mask</b>>
</pre>
<p>In the given command, the <<b>filename mask</b>>
@@ -1282,8 +1282,7 @@
contains the <code>%thread%</code> macro, this file is
thread-specific and access to it is not synchronized.</p>
- <h3><a id="Using_File-name_Masks"
- name="Using_Filename_Masks"></a>5.2.1 Using Filename
+ <h3><a name="Using_Filename_Masks"></a>5.2.1 Using Filename
Masks</h3>
<p>For all streams, the following default filename mask is
@@ -1365,8 +1364,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 id="File_Name_Review"
- name="Filename_Review"></a>5.2.2 Filename Review</h3>
+ <h3><a name="Filename_Review"></a>5.2.2 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
@@ -1388,14 +1386,13 @@
append/truncate mode for the log files that are opened for the
first time:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.append=true
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.append=false
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.append=true
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.append=false
</pre>
<p class="backtotop"><a href="#top">Back to Top</a></p>
- <h2><a id="Using_Stream"
- name="Using_Streams"></a>5.3 Using Streams</h2>
+ <h2><a name="Using_Streams"></a>5.3 Using Streams</h2>
<p>A typical usage pattern for Jitrino action is the
following:</p>
@@ -1432,7 +1429,7 @@
<prefix> <arg def>
<prefix> <file read>
-<prefix> : -Djit.
+<prefix> : -XDjit.
<base> : [ <JIT> . ] [ <pipeline> . ]
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=499820&r1=499819&r2=499820
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html Thu Jan 25 07:35:04 2007
@@ -275,7 +275,7 @@
machine using a combination of the native stack and registers.
</li>
<li>
- <a href="#Architecture">Jitrino.OPT</a> optimizing compiler can
+ <a href="#OPT_Architecture">Jitrino.OPT</a> optimizing compiler can
performs bytecode compilation with a variety of optimizations. The
compiler features two types of code <a href="#IR">intermediate
representation</a> (IR): platform-independent high-level IR (HIR)
@@ -347,7 +347,7 @@
</h2>
<p>
Jitrino compilers provide means to compile and optimize code
- distributed for Java<a href="#*#*">*</a> run-time environments and to
+ distributed for Java<a href="#*">*</a> run-time environments and to
adapt it to various hardware architectures. Figure 1 demonstrates the
architecture of the compilers and their interaction with the <a
href="developers_guide.html">virtual machine</a>.
@@ -389,7 +389,7 @@
<p>
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
+ 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>
@@ -465,7 +465,7 @@
VM properties. Understanding pipeline configuration rules is required
for using the Jitrino command-line interface and effectively
exercising the Jitrino logging system. For details on PMF internals,
- refer to the <a href="Jitrino_PMF.html">PMF Detailed Description</a>.
+ refer to the <a href="JIT_PMF.html">PMF Detailed Description</a>.
</p>
<p class="backtotop">
<a href="#top">Back to Top</a>
@@ -1826,7 +1826,7 @@
counters and time measurement, use the following command syntax:
</p>
<pre>
--Djit.<JIT>.arg.time=on
+-XDjit.<JIT>.arg.time=on
</pre>
<p class="note">
Note
@@ -1954,7 +1954,7 @@
The general syntax of the logging command follows PMF rules:
</p>
<pre>
--Djit.<JIT>.<pipeline>.arg.<path>.log=<list of stream names>
+-XDjit.<JIT>.<pipeline>.arg.<path>.log=<list of stream names>
</pre>
<p>
In this command syntax, <code><path></code> represents the set
@@ -1968,13 +1968,13 @@
To enable compilation protocols for all pipelines of all JITs, type
</p>
<pre class="exampletext">
--Djit.arg.log=info
+-XDjit.arg.log=info
</pre>
<p class="exampletext">
To dump compile-time diagnostic together with IR dumps, type
</p>
<pre class="exampletext">
--Djit.arg.log=ct,irdump
+-XDjit.arg.log=ct,irdump
</pre>
<h3>
5.3.1 CFG Visualization
@@ -1995,11 +1995,11 @@
To enable dumping .dot files, use the following command:
</p>
<pre>
--Djit.arg.log=dotdump
+-XDjit.arg.log=dotdump
</pre>
<p>
For more details on the Jitrino logging system, refer to the
- corresponding section in the <a href="PMF.html">PMF</a> description.
+ corresponding section in the <a href="JIT_PMF.html">PMF</a> description.
</p>
<p class="backtotop">
<a href="#top">Back to Top</a>
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=499820&r1=499819&r2=499820
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino_PMF.html (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino_PMF.html Thu Jan 25 07:35:04 2007
@@ -156,7 +156,7 @@
<p>The document contains the detailed description of the
Jitrino pipeline management framework (PMF). For a high-level
- PMF overview, refer to the <a href="#Jitrino.html">Jitrino
+ PMF overview, refer to the <a href="JIT.html">Jitrino
document</a>.</p>
<h2><a id="Key_Elements"
@@ -288,7 +288,7 @@
</dd>
</dl>
- <p style="text-align: center"><img src="images/Pipeline.PNG"
+ <p style="text-align: center"><img src="images/Pipeline.png"
alt="package" /></p>
<p class="special">Figure 1: The Role of Pipelines in the JIT
@@ -394,14 +394,14 @@
<p>The general form of the JIT command is the following:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.<<b>parameter</b>>=<<b>value</b>>
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.<<b>parameter</b>>=<<b>value</b>>
</pre>
<p>Where</p>
<ul>
<li>
- <code>-Djit.</code> is the mandatory prefix enabling
+ <code>-XDjit.</code> is the mandatory prefix enabling
JIT commands selection from VM commands.
<p class="note">Note</p>
@@ -418,7 +418,7 @@
<p class="note">Note</p>
<p class="notetext">JITs are created by
- <a href="#EM.html">Execution Manager</a> (EM) using
+ <a href="EM.html">Execution Manager</a> (EM) using
information from the command line and/or
<a href="http://incubator.apache.org/harmony/subcomponents/drlvm/emguide.html">
<code>execution manager configuration</code>
@@ -470,13 +470,13 @@
a <i>command file</i> and read this file with a special <i>read
command</i>:</p>
<pre>
--Djit.read=<<b>command filename</b>>
+-XDjit.read=<<b>command filename</b>>
</pre>
<p class="note">Note</p>
<p class="notetext">Write commands in the command file without
- the prefix <code>-Djit</code>. The <code>read</code> command
+ the prefix <code>-XDjit</code>. The <code>read</code> command
itself can be used in the command file. The command file can
contain empty lines and comment lines starting with
<code>#</code> or <code>//</code>.</p>
@@ -505,7 +505,7 @@
non-terminal node of the tree is called a <i>path</i> and
defined by the following <i>path definition</i> command:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.path.<<b>name</b>>=<<b>child1</b>>,<<b>child2</b>>,...
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.path.<<b>name</b>>=<<b>child1</b>>,<<b>child2</b>>,...
</pre>
<p>The given command introduces a node with the specified name
@@ -529,9 +529,9 @@
and <code><b>a</b></code>, <code><b>b</b></code> and
<code><b>c</b></code> are the action names.</p>
<pre>
--Djit.OPT.path=M,N
--Djit.OPT.path.M=a
--Djit.OPT.path.N=b,c
+-XDjit.OPT.path=M,N
+-XDjit.OPT.path.M=a
+-XDjit.OPT.path.N=b,c
</pre>
<p class="exampletext">The given commands describe the simple
@@ -589,7 +589,7 @@
<p>To define a filter, use the following command format:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.filter=<<b>class</b>>.<<b>method</b>><<b>signature</b>>
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.filter=<<b>class</b>>.<<b>method</b>><<b>signature</b>>
</pre>
<p>Where</p>
@@ -624,7 +624,7 @@
<p class="example">Example</p>
<pre>
--Djit.OPT.p.filter=java/lang/Thread.check
+-XDjit.OPT.p.filter=java/lang/Thread.check
</pre>
<p class="exampletext">The following methods can match the
@@ -642,12 +642,12 @@
<p class="example">Example</p>
<pre>
--Djit.OPT.path=M,N
--Djit.OPT.path.M=a
--Djit.OPT.path.N=b,c
--Djit.OPT.p.path=M,N,O
--Djit.OPT.p.path.O=a
--Djit.OPT.p.filter=java/lang/Thread.check
+-XDjit.OPT.path=M,N
+-XDjit.OPT.path.M=a
+-XDjit.OPT.path.N=b,c
+-XDjit.OPT.p.path=M,N,O
+-XDjit.OPT.p.path.O=a
+-XDjit.OPT.p.filter=java/lang/Thread.check
</pre>
<p class="exampletext">The commands above are associated with
@@ -685,7 +685,7 @@
parameters passing convention. The parameter definition command
pattern is the following:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.<<b>param</b>>=<<b>value</b>>
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.<<b>param</b>>=<<b>value</b>>
</pre>
<p>Where</p>
@@ -717,7 +717,7 @@
<p class="example">Example</p>
<pre>
--Djit.OPT.p.arg.a.verify=1
+-XDjit.OPT.p.arg.a.verify=1
</pre>
<p class="exampletext">The given command sets the
@@ -742,7 +742,7 @@
<tr>
<td class="TableCell">
- <code>-Djit.OPT.p.arg.N.b.verify=2</code></td>
+ <code>-XDjit.OPT.p.arg.N.b.verify=2</code></td>
<td class="TableCell">
<center>
@@ -760,7 +760,7 @@
<tr>
<td class="TableCell">
- <code>-Djit.OPT.p.arg.N.verify=2</code></td>
+ <code>-XDjit.OPT.p.arg.N.verify=2</code></td>
<td class="TableCell">
<center>
@@ -775,7 +775,7 @@
<tr>
<td class="TableCell">
- <code>-Djit.OPT.p.arg.verify=2</code></td>
+ <code>-XDjit.OPT.p.arg.verify=2</code></td>
<td class="TableCell"><code><<b>full
name</b>></code></td>
@@ -789,7 +789,7 @@
<tr>
<td class="TableCell">
- <code>-Djit.OPT.arg.N.verify=2</code></td>
+ <code>-XDjit.OPT.arg.N.verify=2</code></td>
<td class="TableCell">
<code><<b>pipeline</b>></code></td>
@@ -805,8 +805,8 @@
<p>The special form of argument definition commands controls
the pipeline construction process:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>=on
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>=off
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>=on
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>=off
</pre>
<p class="note">Note</p>
@@ -826,7 +826,7 @@
<p class="exampletext">To exclude action <code><b>b</b></code>
from the pipeline, apply the following command:</p>
<pre>
--Djit.OPT.p.arg.N.b=off
+-XDjit.OPT.p.arg.N.b=off
</pre>
<p>To enable/disable nodes directly in the path definition
@@ -876,7 +876,7 @@
enabled, <code>c2</code> is disabled and <code>c3</code> is
enabled and mandatory:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.path.<<b>name</b>>=c1+,c2-,c3!
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.path.<<b>name</b>>=c1+,c2-,c3!
</pre>
<p>If you try to disable any mandatory node with the
@@ -891,7 +891,7 @@
pipeline actions. The VM property mechanism fully controls the
system.</p>
- <h2><a id="Stream_Definition"
+ <h2><a
name="Defining_Streams"></a>5.1 Defining Streams</h2>
<p>A set of <i>log streams</i> is used for logging in Jitrino.
@@ -979,7 +979,7 @@
<p>To enable outputting log information to a stream, enter a
command of the following syntax:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log=<<b>stream1</b>>,<<b>stream2</b>>,...
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log=<<b>stream1</b>>,<<b>stream2</b>>,...
</pre>
<p>The left part of the command specifies the name of the JIT
@@ -1009,8 +1009,8 @@
<code><b>N.b</b></code> and <code><b>N.c</b></code> by the same
name. The streams can be assigned to different files.</p>
<pre>
--Djit.OPT.p.arg.N.b.log=ct
--Djit.OPT.p.arg.N.c.log=ct
+-XDjit.OPT.p.arg.N.b.log=ct
+-XDjit.OPT.p.arg.N.c.log=ct
</pre>
<p class="backtotop"><a href="#top">Back to Top</a></p>
@@ -1022,7 +1022,7 @@
<p>To assign a stream to a file, use the following command
syntax:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.file=<<b>filename mask</b>>
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.file=<<b>filename mask</b>>
</pre>
<p>In the given command, the <<b>filename mask</b>>
@@ -1094,8 +1094,7 @@
contains the <code>%thread%</code> macro, this file is
thread-specific and access to it is not synchronized.</p>
- <h3><a id="Using_File-name_Masks"
- name="Using_Filename_Masks"></a>5.2.1 Using Filename
+ <h3><a name="Using_Filename_Masks"></a>5.2.1 Using Filename
Masks</h3>
<p>For all streams, the following default filename mask is
@@ -1177,8 +1176,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 id="File_Name_Review"
- name="Filename_Review"></a>5.2.2 Filename Review</h3>
+ <h3><a name="Filename_Review"></a>5.2.2 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
@@ -1200,14 +1198,13 @@
append/truncate mode for the log files that are opened for the
first time:</p>
<pre>
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.append=true
--Djit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.append=false
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.append=true
+-XDjit.<<b>JIT</b>>.<<b>pipeline</b>>.arg.<<b>full name</b>>.log.<<b>stream</b>>.append=false
</pre>
<p class="backtotop"><a href="#top">Back to Top</a></p>
- <h2><a id="Using_Stream"
- name="Using_Streams"></a>5.3 Using Streams</h2>
+ <h2><a name="Using_Streams"></a>5.3 Using Streams</h2>
<p>A typical usage pattern for Jitrino action is the
following:</p>
@@ -1244,7 +1241,7 @@
<prefix> <arg def>
<prefix> <file read>
-<prefix> : -Djit.
+<prefix> : -XDjit.
<base> : [ <JIT> . ] [ <pipeline> . ]