summaryrefslogtreecommitdiffstats
path: root/docs/instruction-formats.html
diff options
context:
space:
mode:
authorElliott Hughes <enh@google.com>2012-01-04 15:38:58 -0800
committerElliott Hughes <enh@google.com>2012-01-05 10:47:28 -0800
commitab35b50311951feea3782151dd5422ee944685c2 (patch)
tree5f4743612c5c3d1ac48a90e90e39361d40acf7f1 /docs/instruction-formats.html
parentd04ce3821fb7db99685c653b25397e3ca51e5cfd (diff)
downloadandroid_dalvik-ab35b50311951feea3782151dd5422ee944685c2.tar.gz
android_dalvik-ab35b50311951feea3782151dd5422ee944685c2.tar.bz2
android_dalvik-ab35b50311951feea3782151dd5422ee944685c2.zip
Remove unsupported experimental opcodes.
External developers were starting to try to get themselves into trouble with this stuff... Change-Id: I2b03bfeaa8c98b6a994bc7924fc8dcf4e4d4f6cb
Diffstat (limited to 'docs/instruction-formats.html')
-rw-r--r--docs/instruction-formats.html56
1 files changed, 1 insertions, 55 deletions
diff --git a/docs/instruction-formats.html b/docs/instruction-formats.html
index ada1bb26c..f320a2d13 100644
--- a/docs/instruction-formats.html
+++ b/docs/instruction-formats.html
@@ -28,8 +28,7 @@ represents four bits, read from high bits to low, with vertical bars
in sequence from "<code>A</code>" are used to indicate fields within
the format (which then get defined further by the syntax column). The term
"<code>op</code>" is used to indicate the position of an eight-bit
-opcode within the format, and similarly "<code>exop</code>" is used
-to indicate an extended sixteen-bit opcode. A slashed zero
+opcode within the format. A slashed zero
("<code>&Oslash;</code>") is used to indicate that all bits must be
zero in the indicated position.</p>
@@ -455,59 +454,6 @@ the correspondence.</p>
<td><i><code>op</code></i> vAA, #+BBBBBBBBBBBBBBBB</td>
<td>const-wide</td>
</tr>
-<tr>
- <td rowspan="2"><i>exop</i> BB|AA CCCC</td>
- <td>33x</td>
- <td><i><code>exop</code></i> vAA, vBB, vCCCC</td>
- <td>&nbsp;</td>
-</tr>
-<tr>
- <td>32s</td>
- <td><i><code>exop</code></i> vAA, vBB, #+CCCC</td>
- <td>&nbsp;</td>
-</tr>
-<tr>
- <td><i>exop</i> BBBB<sub>lo</sub> BBBB<sub>hi</sub> AAAA</td></td>
- <td>40sc</td>
- <td><i><code>exop</code></i> AAAA, kind@BBBBBBBB</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/>
- <i><code>exop</code></i> vAAAA, type@BBBBBBBB
- <p><i>The unusual choice in lettering here reflects a desire to make
- the letters match their use in related formats 21c and 31c.</i></p>
- </td>
- <td>&nbsp;</td>
-</tr>
-<tr>
- <td><i>exop</i> CCCC<sub>lo</sub> CCCC<sub>hi</sub>
- AAAA BBBB</td>
- <td>52c</td>
- <td><i><code>exop</code></i> vAAAA, vBBBB, field@CCCCCCCC<br/>
- <i><code>exop</code></i> vAAAA, vBBBB, type@CCCCCCCC
- <p><i>The unusual choice in lettering here reflects a desire to make
- the letters match their use in related formats 22c and 22cs.</i></p>
- </td>
- <td>&nbsp;</td>
-</tr>
-<tr>
- <td><i>exop</i> BBBB<sub>lo</sub> BBBB<sub>hi</sub>
- AAAA CCCC</td>
- <td>5rc</td>
- <td><i><code>exop</code></i> {vCCCC .. vNNNN}, meth@BBBBBBBB<br/>
- <i><code>exop</code></i> {vCCCC .. vNNNN}, type@BBBBBBBB<br/>
- <p><i>where <code>NNNN = CCCC+AAAA-1</code>, that is <code>A</code>
- determines the count <code>0..65535</code>, and <code>C</code>
- determines the first register</i></p>
- <p><i>The unusual choice in lettering here reflects a desire to make
- the letters match their use in related formats 3rc, 3rms, and 3rmi.</i></p>
- </td>
- <td>&nbsp;</td>
-</tr>
</tbody>
</table>