From: Adrian Prantl Date: Thu, 23 Mar 2017 20:23:42 +0000 (+0000) Subject: Zero-Initialize PrevInstBB when entering a new MachineFunction. X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5787d18e9cea5563045277310f9dd638dbe6b955;p=llvm Zero-Initialize PrevInstBB when entering a new MachineFunction. It is not guaranteed that the memory used for MachineBasicBlocks in the previous MachineFunction hasn't been freed, so holding on to a pointer to the last function's isn't correct. Particularly I have observed the sret.ll testcase failing because the first BasicBlock in the new function happened to be allocated to the exact same memory as the previously saved and (deleted) PrevInstBB. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@298642 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/lib/CodeGen/AsmPrinter/DebugHandlerBase.cpp b/lib/CodeGen/AsmPrinter/DebugHandlerBase.cpp index aa8b8fbb869..1d63e33a4d3 100644 --- a/lib/CodeGen/AsmPrinter/DebugHandlerBase.cpp +++ b/lib/CodeGen/AsmPrinter/DebugHandlerBase.cpp @@ -130,6 +130,7 @@ bool hasDebugInfo(const MachineModuleInfo *MMI, const MachineFunction *MF) { void DebugHandlerBase::beginFunction(const MachineFunction *MF) { assert(Asm); + PrevInstBB = nullptr; if (!hasDebugInfo(MMI, MF)) { skippedNonDebugFunction();