Recommended: Sing it, brah! 5 fabulous songs for developers
JW's Top 5
Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs
Page 3 of 10
| Opcode | Operand(s) | Description |
|---|---|---|
iconst_m1 |
(none) | pushes int -1 onto the stack |
iconst_0 |
(none) | pushes int 0 onto the stack |
iconst_1 |
(none) | pushes int 1 onto the stack |
iconst_2 |
(none) | pushes int 2 onto the stack |
iconst_3 |
(none) | pushes int 3 onto the stack |
iconst_4 |
(none) | pushes int 4 onto the stack |
iconst_5 |
(none) | pushes int 5 onto the stack |
fconst_0 |
(none) | pushes float 0 onto the stack |
fconst_1 |
(none) | pushes float 1 onto the stack |
fconst_2 |
(none) | pushes float 2 onto the stack |
The opcodes shown in the previous table push ints and floats, which are 32-bit values. Each slot on the Java stack is 32 bits wide. Therefore each time an int or float is pushed onto the stack, it occupies one slot.
The opcodes shown in the next table push longs and doubles. Long and double values occupy 64 bits. Each time a long or double is pushed onto the stack, its value occupies two slots on the stack. Opcodes that indicate a specific long or double value to push are shown in the following table: