The counter of the number of instructions seen in FindAllMemoryUses
is reset after returning from a recursive invocation of FindAllMemoryUses
to the value it had before the call. In effect, depending on the shape of the uses
graph, the function may scan up to 2^N-1 instructions where N is the scan limit
(MaxMemoryUsesToScan). This does not look intuitive or intended.
This patch changes the counting to just count the scanned instructions, independent
of the shape of the references.
Precommit test and use utils/update_llc_test_checks.py script to show what changed?