harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gshiman...@apache.org
Subject svn commit: r652384 - in /harmony/standard/site: docs/subcomponents/drlvm/breakpoints_and_ss.html docs/subcomponents/drlvm/index.html xdocs/subcomponents/drlvm/breakpoints_and_ss.html xdocs/subcomponents/drlvm/index.xml
Date Wed, 30 Apr 2008 14:15:21 GMT
Author: gshimansky
Date: Wed Apr 30 07:15:20 2008
New Revision: 652384

URL: http://svn.apache.org/viewvc?rev=652384&view=rev
Log:
Fixed formatting of lists in index and breakpoints documents


Modified:
    harmony/standard/site/docs/subcomponents/drlvm/breakpoints_and_ss.html
    harmony/standard/site/docs/subcomponents/drlvm/index.html
    harmony/standard/site/xdocs/subcomponents/drlvm/breakpoints_and_ss.html
    harmony/standard/site/xdocs/subcomponents/drlvm/index.xml

Modified: harmony/standard/site/docs/subcomponents/drlvm/breakpoints_and_ss.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/breakpoints_and_ss.html?rev=652384&r1=652383&r2=652384&view=diff
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/breakpoints_and_ss.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/breakpoints_and_ss.html Wed Apr 30 07:15:20
2008
@@ -388,43 +388,37 @@
 </p>
 <ol>
   <li>
-    <p>Removes all breakpoints predicted for the current thread
-      - they were used on the previous step.</p>
+    Removes all breakpoints predicted for the current thread
+      - they were used on the previous step.
     <li>
-      <p>Depending on the currently executed bytecode, predicts
-        which bytecode(s) may be executed next to it.</p>
+      Depending on the currently executed bytecode, predicts
+        which bytecode(s) may be executed next to it.
       <ol>
         <li>
-          <p>For ordinary bytecodes that don't transfer execution control the
+          For ordinary bytecodes that don't transfer execution control the
             next bytecode is the one next to the current one in the method's
-            bytecode array.</p>
+            bytecode array.
           <li>
-            <p>For bytecodes that transfer control, all of the
+            For bytecodes that transfer control, all of the
               possible target locations are counted as predicted
-              locations.</p>
+              locations.
       </ol>
 </ol>
 <p>JVMTI code doesn't try to interpret the Java state and
 determine which target location is going to take place when the bytecode is
 executed. Instead, JVMTI does the following:</p>
 <ul>
-  <ul>
     <li>
-      <p>For bytecodes like tableswitch and conditional
+      For bytecodes like tableswitch and conditional
         branches, JVMTI adds all its targets to the predicted bytecodes
-        list.</p>
-  </ul>
-</ul>
-<ul>
-  <ul>
+        list.
     <li>
-      <p>For invokestatic and invokespecial bytecodes, the
+      For invokestatic and invokespecial bytecodes, the
         target bytecode is the 1<sup>st</sup> bytecode of the method that they
-        invoke.</p>
+        invoke.
       <li>
-        <p>For invokevirtual and invokeinterface, JVMTI does
-          special handling (<a href="#invoke">see below</a>).</p>
-  </ul>
+        For invokevirtual and invokeinterface, JVMTI does
+          special handling (<a href="#invoke">see below</a>).
 </ul>
 <p>If the target method is not compiled yet, single-step
 breakpoints are added to its list of pending breakpoints in the same way as

Modified: harmony/standard/site/docs/subcomponents/drlvm/index.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/index.html?rev=652384&r1=652383&r2=652384&view=diff
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/index.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/index.html Wed Apr 30 07:15:20 2008
@@ -308,13 +308,6 @@
             </li>
             </ul>
             <li>
-               <a href="JVMTI-PopFrame.html">JVMTI PopFrame Implementation</a>
-             <br />
-              Details on the PopFrame implementation as currently done in DRLVM. 
-              The document indicates the functions responsible for the operation and 
-              gives info on specifics of the current implementation. 
-            </li>
-            <li>
                <a href="verifier.html">Bytecode Verifier</a>
              <br />
               Technical Details for Harmony Bytecode Verifier, including algorithm description.
@@ -343,9 +336,21 @@
               communicates with the rest of VM application.
             </li>
             <li>
-              Implementation of <a href="breakpoints_and_ss.html">breakpoints and single
step</a>
-              JVMTI functionality in JIT mode.
+              Implementation of <a href="http://java.sun.com/j2se/1.5.0/docs/guide/jvmti/jvmti.html">JVMTI
API</a> components in DRLVM
             </li>
+              <ul>
+              <li>
+                Implementation of <a href="breakpoints_and_ss.html">breakpoints and
single step</a>
+                JVMTI functionality in JIT mode.
+              </li>
+              <li>
+               <a href="JVMTI-PopFrame.html">JVMTI PopFrame Implementation</a>
+               <br />
+                Details on the PopFrame implementation as currently done in DRLVM. 
+                The document indicates the functions responsible for the operation and 
+                gives info on specifics of the current implementation. 
+              </li>
+              </ul>
           </ul>
           
         <li><a href="DoxygenStart.html">DRLVM Source Code Generated Documentation
Index</a>

Modified: harmony/standard/site/xdocs/subcomponents/drlvm/breakpoints_and_ss.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/breakpoints_and_ss.html?rev=652384&r1=652383&r2=652384&view=diff
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/breakpoints_and_ss.html (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/breakpoints_and_ss.html Wed Apr 30 07:15:20
2008
@@ -192,43 +192,37 @@
 </p>
 <ol>
   <li>
-    <p>Removes all breakpoints predicted for the current thread
-      - they were used on the previous step.</p>
+    Removes all breakpoints predicted for the current thread
+      - they were used on the previous step.
     <li>
-      <p>Depending on the currently executed bytecode, predicts
-        which bytecode(s) may be executed next to it.</p>
+      Depending on the currently executed bytecode, predicts
+        which bytecode(s) may be executed next to it.
       <ol>
         <li>
-          <p>For ordinary bytecodes that don't transfer execution control the
+          For ordinary bytecodes that don't transfer execution control the
             next bytecode is the one next to the current one in the method's
-            bytecode array.</p>
+            bytecode array.
           <li>
-            <p>For bytecodes that transfer control, all of the
+            For bytecodes that transfer control, all of the
               possible target locations are counted as predicted
-              locations.</p>
+              locations.
       </ol>
 </ol>
 <p>JVMTI code doesn't try to interpret the Java state and
 determine which target location is going to take place when the bytecode is
 executed. Instead, JVMTI does the following:</p>
 <ul>
-  <ul>
     <li>
-      <p>For bytecodes like tableswitch and conditional
+      For bytecodes like tableswitch and conditional
         branches, JVMTI adds all its targets to the predicted bytecodes
-        list.</p>
-  </ul>
-</ul>
-<ul>
-  <ul>
+        list.
     <li>
-      <p>For invokestatic and invokespecial bytecodes, the
+      For invokestatic and invokespecial bytecodes, the
         target bytecode is the 1<sup>st</sup> bytecode of the method that they
-        invoke.</p>
+        invoke.
       <li>
-        <p>For invokevirtual and invokeinterface, JVMTI does
-          special handling (<a href="#invoke">see below</a>).</p>
-  </ul>
+        For invokevirtual and invokeinterface, JVMTI does
+          special handling (<a href="#invoke">see below</a>).
 </ul>
 <p>If the target method is not compiled yet, single-step
 breakpoints are added to its list of pending breakpoints in the same way as

Modified: harmony/standard/site/xdocs/subcomponents/drlvm/index.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/index.xml?rev=652384&r1=652383&r2=652384&view=diff
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/index.xml (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/index.xml Wed Apr 30 07:15:20 2008
@@ -133,13 +133,6 @@
             </li>
             </ul>
             <li>
-               <a href="JVMTI-PopFrame.html">JVMTI PopFrame Implementation</a>
-             <br />
-              Details on the PopFrame implementation as currently done in DRLVM. 
-              The document indicates the functions responsible for the operation and 
-              gives info on specifics of the current implementation. 
-            </li>
-            <li>
                <a href="verifier.html">Bytecode Verifier</a>
              <br />
               Technical Details for Harmony Bytecode Verifier, including algorithm description.
@@ -168,9 +161,21 @@
               communicates with the rest of VM application.
             </li>
             <li>
-              Implementation of <a href="breakpoints_and_ss.html">breakpoints and single
step</a>
-              JVMTI functionality in JIT mode.
+              Implementation of <a href="http://java.sun.com/j2se/1.5.0/docs/guide/jvmti/jvmti.html">JVMTI
API</a> components in DRLVM
             </li>
+              <ul>
+              <li>
+                Implementation of <a href="breakpoints_and_ss.html">breakpoints and
single step</a>
+                JVMTI functionality in JIT mode.
+              </li>
+              <li>
+               <a href="JVMTI-PopFrame.html">JVMTI PopFrame Implementation</a>
+               <br />
+                Details on the PopFrame implementation as currently done in DRLVM. 
+                The document indicates the functions responsible for the operation and 
+                gives info on specifics of the current implementation. 
+              </li>
+              </ul>
           </ul>
           
         <li><a href="DoxygenStart.html">DRLVM Source Code Generated Documentation
Index</a>



Mime
View raw message