We currently use indy for linking optimistic arithmetic operations. This is somewhat wasteful, as we'll have to use INVOKEDYNAMIC (5 bytecodes) + a CP entry, as well as go through a bootstrap method and create a ConstantCallSite. This can be replaced with an INVOKESTATIC (3 bytecodes). It will add explicit loading of program point through either ICONST, BIPUSH, SIPUSH, or LDC, adding between 1-3 bytes to the instruction, so the call site length in the bytecode will be between 4-6 bytes instead of the fix 5, but I expect there will overall be both bytecode size, runtime size, and execution time savings as we will not need all of the extra stuff (call site object, bootstrap invocation, bootstrap descriptor in CP)