[PATCH] D64650: Add a TargetMachineVerifier that runs along with the existing MachineVerifier

[JF Bastien via Phabricator via llvm-commits]

jfb added a comment.

Right, it seems like we might want the following information:

- Value is one of 256 bytes were tracking.
- Value wasn't something we looked into, for X bytes.
- Value was `undef`.
- Value was padding (same as `undef`).

We can figure out some of this, but not all, from the current patch. Is it useful to know the rest? I'm not sure! I haven't inspected all uses to be able to convince myself.


Repository:
  rL LLVM

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D64650/new/

https://reviews.llvm.org/D64650