Dave Bartolomeo 533eeff7e8 C++: Fix MemoryLocation with multiple VirtualVariables ...

While investigating a bug with `TInstruction` sharing, I discovered that we had a case where alias analysis could create two `VirtualVariable`s for the same `Allocation`. For an indirect parameter allocation, we were using the type of the pointer variable as the type of the indirect allocation, instead of just `Unknown`. If the `IRType` of the pointer variable was the same type as the type of at least one access to the indirect allocation, we'd create both an `EntireAllocationVirtualVariable` and a `VariableVirtualVariable` for the allocation.

I added a new consistency test to guard against this in the future. This also turned out to be the root cause of the one existing known consistency failure in the IR tests.

2020-05-27 14:06:59 -04:00

..

ir

C++: Fix MemoryLocation with multiple VirtualVariables

2020-05-27 14:06:59 -04:00

offbyone

C++/C#: Move sanity check inside InstructionSanity module and accept tests

2020-02-23 20:53:49 +01:00

rangeanalysis

C++/C#: Move sanity check inside InstructionSanity module and accept tests

2020-02-23 20:53:49 +01:00