...| putfield | |
| indexbyte1 | |
| indexbyte2 |
Stack
..., objectref, value ...
Stack
..., objectref, value.word1, value.word2 ...
Description
The unsigned indexbyte1 and indexbyte2 are used to construct an index into the constant pool of the current class (§3.6), where the value of the index is (indexbyte1 << 8) | indexbyte2. The constant pool item at the index must be a CONSTANT_Fieldref (§4.4.2), a reference to a class name and a field name. If the field is protected (§4.6), then it must be either a member of the current class or a member of a superclass of the current class, and the class of objectref must be either the current class or a subclass of the current class.
The constant pool item is resolved (§5.2), determining both the field width and the field offset. The type of a value stored by a putfield instruction must be compatible with the descriptor of the field (§4.3.2) of the class instance being stored into. If the field descriptor type is byte, char, short, or int, then the value must be an int. If the field descriptor type is float, long, or double, then the value must be a float, long, or double, respectively. If the field descriptor type is a reference type, then the value must be of a type that is assignment compatible (§2.6.6) with the field descriptor type.
The value and objectref, which must be of type reference, are popped from the operand stack. The field at the offset from the start of the object referenced by objectref is set to the value.
Linking Exceptions
During resolution of the CONSTANT_Fieldref constant pool item, any of the exceptions documented in §5.2 can be thrown.
Otherwise, if the specified field exists but is a static field, putfield throws an IncompatibleClassChangeError.
Runtime Exception
Otherwise, if objectref is null, the putfield instruction throws a NullPointerException.
Notes The putfield instruction operates on both one- and two-word wide fields.