Lines Matching full:code
37 which describes a 16-bit code unit. Each character in a word
39 ("<code>|</code>") interspersed to aid in reading. Uppercase letters
40 in sequence from "<code>A</code>" are used to indicate fields within
42 "<code>op</code>" is used to indicate the position of an eight-bit
44 ("<code>Ø</code>") is used to indicate that all bits must be
47 <p>For the most part, lettering proceeds from earlier code units to
48 later code units, and low-order to high-order within a code unit.
54 <p>For example, the format "<code>B|A|<i>op</i> CCCC</code>" indicates
55 that the format consists of two 16-bit code units. The first word
63 for the format, which is used in other documents and in code to identify
67 letter. The first digit indicates the number of 16-bit code units in the
70 number of registers), with the special designation "<code>r</code>" indicating
73 format "<code>21t</code>" is of length two, contains one register reference,
77 "<code>s</code>" suffix, making them four characters total. Similarly,
78 suggested "inline" linking formats have an additional "<code>i</code>"
82 "<code>20bc</code>") include two pieces of data which are both
117 value; low-order bits are all <code>0</code>)
168 "<code>BB</code>" in the first column would also be labeled
169 "<code>BB</code>" in the syntax column.</p>
171 <p>Arguments which name a register have the form "<code>v<i>X</i></code>".
172 The prefix "<code>v</code>" was chosen instead of the more common
173 "<code>r</code>" exactly to avoid conflicting with (non-virtual) architectures
175 use the prefix "<code>r</code>" for their registers. (That is, this
180 "<code>#+<i>X</i></code>". Some formats indicate literals that only
186 form "<code>+<i>X</i></code>".</p>
189 "<code><i>kind</i>@<i>X</i></code>", where "<code><i>kind</i></code>"
193 kinds of constant pool are "<code>string</code>" (string pool index),
194 "<code>type</code>" (type pool index), "<code>field</code>" (field
195 pool index), and "<code>meth</code>" (method pool index).</p>
200 (indicated as "<code>vtaboff</code>") and field offsets (indicated as
201 "<code>fieldoff</code>").</p>
205 "<code>[<i>X</i>=<i>N</i>]</code>" (e.g., "<code>[A=2]</code>") to indicate
223 <td><i><code>N/A</code></i></td>
230 <td><i><code>op</code></i></td>
236 <td><i><code>op</code></i> vA, vB</td>
241 <td><i><code>op</code></i> vA, #+B</td>
247 <td><i><code>op</code></i> vAA</td>
252 <td><i><code>op</code></i> +AA</td>
258 <td><i><code>op</code></i> +AAAA</td>
264 <td><i><code>op</code></i> AA, kind@BBBB</td>
272 <td><i><code>op</code></i> vAA, vBBBB</td>
277 <td><i><code>op</code></i> vAA, +BBBB</td>
282 <td><i><code>op</code></i> vAA, #+BBBB</td>
287 <td><i><code>op</code></i> vAA, #+BBBB0000<br/>
288 <i><code>op</code></i> vAA, #+BBBB000000000000
294 <td><i><code>op</code></i> vAA, type@BBBB<br/>
295 <i><code>op</code></i> vAA, field@BBBB<br/>
296 <i><code>op</code></i> vAA, string@BBBB
306 <td><i><code>op</code></i> vAA, vBB, vCC</td>
311 <td><i><code>op</code></i> vAA, vBB, #+CC</td>
317 <td><i><code>op</code></i> vA, vB, +CCCC</td>
322 <td><i><code>op</code></i> vA, vB, #+CCCC</td>
327 <td><i><code>op</code></i> vA, vB, type@CCCC<br/>
328 <i><code>op</code></i> vA, vB, field@CCCC
334 <td><i><code>op</code></i> vA, vB, fieldoff@CCCC</td>
342 <td><i><code>op</code></i> +AAAAAAAA</td>
348 <td><i><code>op</code></i> vAAAA, vBBBB</td>
354 <td><i><code>op</code></i> vAA, #+BBBBBBBB</td>
359 <td><i><code>op</code></i> vAA, +BBBBBBBB</td>
364 <td><i><code>op</code></i> vAA, string@BBBBBBBB</td>
370 <td><i>[<code>A=5</code>] <code>op</code></i> {vC, vD, vE, vF, vG},
372 <i>[<code>A=5</code>] <code>op</code></i> {vC, vD, vE, vF, vG},
374 <i>[<code>A=4</code>] <code>op</code></i> {vC, vD, vE, vF},
375 <i><code>kind</code></i>@BBBB<br/>
376 <i>[<code>A=3</code>] <code>op</code></i> {vC, vD, vE},
377 <i><code>kind</code></i>@BBBB<br/>
378 <i>[<code>A=2</code>] <code>op</code></i> {vC, vD},
379 <i><code>kind</code></i>@BBBB<br/>
380 <i>[<code>A=1</code>] <code>op</code></i> {vC},
381 <i><code>kind</code></i>@BBBB<br/>
382 <i>[<code>A=0</code>] <code>op</code></i> {},
383 <i><code>kind</code></i>@BBBB<br/>
392 <td><i>[<code>A=5</code>] <code>op</code></i> {vC, vD, vE, vF, vG},
394 <i>[<code>A=4</code>] <code>op</code></i> {vC, vD, vE, vF},
396 <i>[<code>A=3</code>] <code>op</code></i> {vC, vD, vE},
398 <i>[<code>A=2</code>] <code>op</code></i> {vC, vD},
400 <i>[<code>A=1</code>] <code>op</code></i> {vC},
406 <td><i>suggested format for statically linked <code>invoke-virtual</code>
407 and <code>invoke-super</code> instructions of format 35c</i>
412 <td><i>[<code>A=5</code>] <code>op</code></i> {vC, vD, vE, vF, vG},
414 <i>[<code>A=4</code>] <code>op</code></i> {vC, vD, vE, vF},
416 <i>[<code>A=3</code>] <code>op</code></i> {vC, vD, vE},
418 <i>[<code>A=2</code>] <code>op</code></i> {vC, vD},
420 <i>[<code>A=1</code>] <code>op</code></i> {vC},
426 <td><i>suggested format for inline linked <code>invoke-static</code>
427 and <code>invoke-virtual</code> instructions of format 35c</i>
433 <td><i><code>op</code></i> {vCCCC .. vNNNN}, meth@BBBB<br/>
434 <i><code>op</code></i> {vCCCC .. vNNNN}, type@BBBB<br/>
435 <p><i>where <code>NNNN = CCCC+AA-1</code>, that is <code>A</code>
436 determines the count <code>0..255</code>, and <code>C</code>
443 <td><i><code>op</code></i> {vCCCC .. vNNNN}, vtaboff@BBBB<br/>
444 <p><i>where <code>NNNN = CCCC+AA-1</code>, that is <code>A</code>
445 determines the count <code>0..255</code>, and <code>C</code>
448 <td><i>suggested format for statically linked <code>invoke-virtual</code>
449 and <code>invoke-super</code> instructions of format <code>3rc</code></i>
454 <td><i><code>op</code></i> {vCCCC .. vNNNN}, inline@BBBB<br/>
455 <p><i>where <code>NNNN = CCCC+AA-1</code>, that is <code>A</code>
456 determines the count <code>0..255</code>, and <code>C</code>
459 <td><i>suggested format for inline linked <code>invoke-static</code>
460 and <code>invoke-virtual</code> instructions of format 3rc</i>
466 <td><i><code>op</code></i> vAA, #+BBBBBBBBBBBBBBBB</td>
