Over in D104684 we ended up creating duplicate instruction numbers for instruction-referencing mode (root cause: I haven't landed the docs in D113586). A new pattern for optimising LEAs is added, and the instruction number for the computed value is attached to two instructions, not one. This then causes an assertion to fire in EXPENSIVE_CHECKS mode as reported by @uabelho in [0]. This patch removes the duplicate instruction number and adds a test.
Without EXPENSIVE_CHECKs, the net effect is that the developer will be presented with the wrong variable location, so this shouldn't be crashing anywhere else. However, that's a good argument for adding more instr-ref checks to MachineVerifier.
(This patch also modifies a COREI7-LABEL line that looks like it was typo'd when I originally landed the test, ooof. It doesn't affect test coverage until this patch though).
Nice drive-by fix.