Lines Matching full:code
31 which describes a 16-bit code unit. Each character in a word
33 ("<code>|</code>") interspersed to aid in reading. Uppercase letters
34 in sequence from "<code>A</code>" are used to indicate fields within
36 "<code>op</code>" is used to indicate the position of an eight-bit
38 ("<code>Ø</code>") is used to indicate that all bits must be
41 <p>For the most part, lettering proceeds from earlier code units to
42 later code units, and low-order to high-order within a code unit.
48 <p>For example, the format "<code>B|A|<i>op</i> CCCC</code>" indicates
49 that the format consists of two 16-bit code units. The first word
57 for the format, which is used in other documents and in code to identify
61 letter. The first digit indicates the number of 16-bit code units in the
64 number of registers), with the special designation "<code>r</code>" indicating
67 format "<code>21t</code>" is of length two, contains one register reference,
71 "<code>s</code>" suffix, making them four characters total. Similarly,
72 suggested "inline" linking formats have an additional "<code>i</code>"
76 "<code>20bc</code>") include two pieces of data which are both
111 value; low-order bits are all <code>0</code>)
162 "<code>BB</code>" in the first column would also be labeled
163 "<code>BB</code>" in the syntax column.</p>
165 <p>Arguments which name a register have the form "<code>v<i>X</i></code>".
166 The prefix "<code>v</code>" was chosen instead of the more common
167 "<code>r</code>" exactly to avoid conflicting with (non-virtual) architectures
169 use the prefix "<code>r</code>" for their registers. (That is, this
174 "<code>#+<i>X</i></code>". Some formats indicate literals that only
180 form "<code>+<i>X</i></code>".</p>
183 "<code><i>kind</i>@<i>X</i></code>", where "<code><i>kind</i></code>"
187 kinds of constant pool are "<code>string</code>" (string pool index),
188 "<code>type</code>" (type pool index), "<code>field</code>" (field
189 pool index), and "<code>meth</code>" (method pool index).</p>
194 (indicated as "<code>vtaboff</code>") and field offsets (indicated as
195 "<code>fieldoff</code>").</p>
199 "<code>[<i>X</i>=<i>N</i>]</code>" (e.g., "<code>[A=2]</code>") to indicate
217 <td><i><code>N/A</code></i></td>
224 <td><i><code>op</code></i></td>
230 <td><i><code>op</code></i> vA, vB</td>
235 <td><i><code>op</code></i> vA, #+B</td>
241 <td><i><code>op</code></i> vAA</td>
246 <td><i><code>op</code></i> +AA</td>
252 <td><i><code>op</code></i> +AAAA</td>
258 <td><i><code>op</code></i> AA, kind@BBBB</td>
266 <td><i><code>op</code></i> vAA, vBBBB</td>
271 <td><i><code>op</code></i> vAA, +BBBB</td>
276 <td><i><code>op</code></i> vAA, #+BBBB</td>
281 <td><i><code>op</code></i> vAA, #+BBBB0000<br/>
282 <i><code>op</code></i> vAA, #+BBBB000000000000
288 <td><i><code>op</code></i> vAA, type@BBBB<br/>
289 <i><code>op</code></i> vAA, field@BBBB<br/>
290 <i><code>op</code></i> vAA, string@BBBB
300 <td><i><code>op</code></i> vAA, vBB, vCC</td>
305 <td><i><code>op</code></i> vAA, vBB, #+CC</td>
311 <td><i><code>op</code></i> vA, vB, +CCCC</td>
316 <td><i><code>op</code></i> vA, vB, #+CCCC</td>
321 <td><i><code>op</code></i> vA, vB, type@CCCC<br/>
322 <i><code>op</code></i> vA, vB, field@CCCC
328 <td><i><code>op</code></i> vA, vB, fieldoff@CCCC</td>
336 <td><i><code>op</code></i> +AAAAAAAA</td>
342 <td><i><code>op</code></i> vAAAA, vBBBB</td>
348 <td><i><code>op</code></i> vAA, #+BBBBBBBB</td>
353 <td><i><code>op</code></i> vAA, +BBBBBBBB</td>
358 <td><i><code>op</code></i> vAA, string@BBBBBBBB</td>
364 <td><i>[<code>A=5</code>] <code>op</code></i> {vC, vD, vE, vF, vG},
366 <i>[<code>A=5</code>] <code>op</code></i> {vC, vD, vE, vF, vG},
368 <i>[<code>A=4</code>] <code>op</code></i> {vC, vD, vE, vF},
369 <i><code>kind</code></i>@BBBB<br/>
370 <i>[<code>A=3</code>] <code>op</code></i> {vC, vD, vE},
371 <i><code>kind</code></i>@BBBB<br/>
372 <i>[<code>A=2</code>] <code>op</code></i> {vC, vD},
373 <i><code>kind</code></i>@BBBB<br/>
374 <i>[<code>A=1</code>] <code>op</code></i> {vC},
375 <i><code>kind</code></i>@BBBB<br/>
376 <i>[<code>A=0</code>] <code>op</code></i> {},
377 <i><code>kind</code></i>@BBBB<br/>
386 <td><i>[<code>A=5</code>] <code>op</code></i> {vC, vD, vE, vF, vG},
388 <i>[<code>A=4</code>] <code>op</code></i> {vC, vD, vE, vF},
390 <i>[<code>A=3</code>] <code>op</code></i> {vC, vD, vE},
392 <i>[<code>A=2</code>] <code>op</code></i> {vC, vD},
394 <i>[<code>A=1</code>] <code>op</code></i> {vC},
400 <td><i>suggested format for statically linked <code>invoke-virtual</code>
401 and <code>invoke-super</code> instructions of format 35c</i>
406 <td><i>[<code>A=5</code>] <code>op</code></i> {vC, vD, vE, vF, vG},
408 <i>[<code>A=4</code>] <code>op</code></i> {vC, vD, vE, vF},
410 <i>[<code>A=3</code>] <code>op</code></i> {vC, vD, vE},
412 <i>[<code>A=2</code>] <code>op</code></i> {vC, vD},
414 <i>[<code>A=1</code>] <code>op</code></i> {vC},
420 <td><i>suggested format for inline linked <code>invoke-static</code>
421 and <code>invoke-virtual</code> instructions of format 35c</i>
427 <td><i><code>op</code></i> {vCCCC .. vNNNN}, meth@BBBB<br/>
428 <i><code>op</code></i> {vCCCC .. vNNNN}, type@BBBB<br/>
429 <p><i>where <code>NNNN = CCCC+AA-1</code>, that is <code>A</code>
430 determines the count <code>0..255</code>, and <code>C</code>
437 <td><i><code>op</code></i> {vCCCC .. vNNNN}, vtaboff@BBBB<br/>
438 <p><i>where <code>NNNN = CCCC+AA-1</code>, that is <code>A</code>
439 determines the count <code>0..255</code>, and <code>C</code>
442 <td><i>suggested format for statically linked <code>invoke-virtual</code>
443 and <code>invoke-super</code> instructions of format <code>3rc</code></i>
448 <td><i><code>op</code></i> {vCCCC .. vNNNN}, inline@BBBB<br/>
449 <p><i>where <code>NNNN = CCCC+AA-1</code>, that is <code>A</code>
450 determines the count <code>0..255</code>, and <code>C</code>
453 <td><i>suggested format for inline linked <code>invoke-static</code>
454 and <code>invoke-virtual</code> instructions of format 3rc</i>
460 <td><i><code>op</code></i> vAA, #+BBBBBBBBBBBBBBBB</td>
