Don't accidentally create MachineFunctions in mir-debugify/mir-strip-debugify
authorDaniel Sanders <daniel_l_sanders@apple.com>
Fri, 17 Apr 2020 17:24:35 +0000 (10:24 -0700)
committerDaniel Sanders <daniel_l_sanders@apple.com>
Fri, 17 Apr 2020 21:28:41 +0000 (14:28 -0700)
commit14ad8dc0761a1e440304a03a1f4828280cf112e2
treec07dd9c8375e76e0560a4ad1edfbef86cd77cadf
parentef49b1d97e1ac75bff8ff7dec3097b43bcd07e73
Don't accidentally create MachineFunctions in mir-debugify/mir-strip-debugify

We should only modify existing ones. Previously, we were creating
MachineFunctions for externally-available functions. AFAICT this was benign
in tree but ultimately led to asan bugs in our out of tree target.
llvm/lib/CodeGen/MachineDebugify.cpp
llvm/lib/CodeGen/MachineStripDebug.cpp