An interesting phenomenon about xload_0 like instructions

Question

I have noticed a phenomenon:
when an object is instanciated by the "new" instruc- tion, the JVM will first create an object of its father class and instanciate the object (you can find aload_0 invo- ke_special 0,1in its init method), then store the already prepared reference of father class's object into its local variable with index 0(by instruction "aload_0").
I also noticed:
In the "main(String args[])" method, if you want to use
args[0], the bytecode for such use is "aload_0 iconst_0
aaload", the sequence tells us that JVM referenced the
local variable with index 0 which holds the args reference
,then the array item's index will be obtained from operand
stack, and the item can then be found.
But I have never found the use of "iload_0".Thus I wond-er whether the local variable with index 0 is set aside for these two kinds of use.If so, the instruction "iload_0" can never be used.

Answer 1

Therefore, only a static method can use iload_0:
    static int foo(int i) {
        return i;
    }is compiled into:
Method int foo(int)
   0 iload_0
   1 ireturn