Dave Bartolomeo fa2ef620ac C++: Rationalize RegisterOperand vs. MemoryOperand ...

This change does some shuffling to make the distinction between memory operands and register operands more clear in the IR API. First, any given type that extends `Operand` is now either always a `MemoryOperand` or always a `RegisterOperand`. This required getting rid of `CopySourceOperand`, which was used for both the `CopyValue` instruction (as a `RegisterOperand`) and for the `Load` instruction (as a `MemoryOperand`). `CopyValue` is now just a `UnaryInstruction`, `Store` has a `StoreValueOperand` (`RegisterOperand`), and all of the instructions that read a value from memory indirectly (`Load`, `ReturnValue`, and `ThrowValue`) all now have a `LoadOperand` (`MemoryOperand`).

There are no diffs in the IR output for this commit, but this change is required for a subsequent commit that will make each `MemoryOperand` have a `Type`, which in turn is needed to fix a critical bug in aliased SSA construction.

2019-02-11 09:47:00 -08:00

..

src

C++: Rationalize RegisterOperand vs. MemoryOperand

2019-02-11 09:47:00 -08:00

test

C++: Split out SSA IR tests

2019-02-08 15:28:06 -08:00