summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorDan Bornstein <danfuzz@android.com>2010-12-10 16:57:38 -0800
committerDan Bornstein <danfuzz@android.com>2010-12-10 16:58:19 -0800
commitfa2f5add0e833f2c90cbceb13cee5a28d4a29c6b (patch)
tree5aea015b877067139a7ca66e0eaf1aa3db13c9b1 /docs
parente91b6e1f666cf2d032971b190205d6574e631be9 (diff)
downloadandroid_dalvik-fa2f5add0e833f2c90cbceb13cee5a28d4a29c6b.tar.gz
android_dalvik-fa2f5add0e833f2c90cbceb13cee5a28d4a29c6b.tar.bz2
android_dalvik-fa2f5add0e833f2c90cbceb13cee5a28d4a29c6b.zip
New instruction format for verification errors.
Change-Id: I99e6828487dcc7f6277bb710e4279ce0aa8c7563
Diffstat (limited to 'docs')
-rw-r--r--docs/instruction-formats.html25
1 files changed, 18 insertions, 7 deletions
diff --git a/docs/instruction-formats.html b/docs/instruction-formats.html
index e9e4140c9..2a81e607d 100644
--- a/docs/instruction-formats.html
+++ b/docs/instruction-formats.html
@@ -62,13 +62,14 @@ indicates the type of any extra data encoded by the format. For example,
format "<code>21t</code>" is of length two, contains one register reference,
and additionally contains a branch target.</p>
-<p>Suggested static linking formats have an additional "<code>s</code>" suffix,
-making them four characters total. Similarly, suggested "inline" linking
-formats have an additional "<code>i</code>" suffix. (In this context, inline
-linking is like static linking, except with more direct ties into a
-virtual machine's implementation.) Finally, one oddball suggested format
-("<code>20bc</code>") includes two pieces of data which are represented in
-its format ID.</p>
+<p>Suggested static linking formats have an additional
+"<code>s</code>" suffix, making them four characters total. Similarly,
+suggested "inline" linking formats have an additional "<code>i</code>"
+suffix. (In this context, inline linking is like static linking,
+except with more direct ties into a virtual machine's implementation.)
+Finally, a couple oddball suggested formats (e.g.,
+"<code>20bc</code>") include two pieces of data which are both
+represented in its format ID.</p>
<p>The full list of typecode letters are as follows. Note that some
forms have different sizes, depending on the format:</p>
@@ -466,6 +467,16 @@ the correspondence.</p>
<td>&nbsp;</td>
</tr>
<tr>
+ <td><i>exop</i> BBBB AAAA<sub>lo</sub> AAAA<sub>hi</sub></td></td>
+ <td>40bc</td>
+ <td><i><code>exop</code></i> BBBB, kind@AAAAAAAA
+ <p><i>The unusual choice in lettering here reflects a desire to make
+ the letters match their use in related format 20bc.</i></p>
+ </td>
+ <td><i>suggested format for statically determined verification errors;
+ see <code>20bc</code>, above</i></td>
+</tr>
+<tr>
<td><i>exop</i> BBBB<sub>lo</sub> BBBB<sub>hi</sub> AAAA
<td>41c</td>
<td><i><code>exop</code></i> vAAAA, field@BBBBBBBB<br/>