MCSymbolizer::tryAddingSymbolicOperand() overloaded the Size parameter
to specify either the instruction size or the operand size depending on
the architecture. However, for proper symbolic disassembly on X86, we
need to know both sizes, as an instruction can have two operands and
the instruction size cannot be calculated based on an operand offset
and its size. Hence, split Size into OpSize and InstSize.
For X86, the new interface allows to fix a couple of issues:
- Correctly adjust the value of PC-relative operands.
- Set operand size to zero when the operand is specified implicitly.
Why is "0" used as argument here? Is it unused?