From: Dan Gohman Date: Fri, 18 Jun 2010 15:36:18 +0000 (+0000) Subject: Don't call clear() on DbgInfo when it's going to be deleted anyway. X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=c97df860dd8172077c9b3b086c192f1b05365699;p=oota-llvm.git Don't call clear() on DbgInfo when it's going to be deleted anyway. Don't replace the old DbgInfo with a new one when clear() on the old one is sufficient. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@106283 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/lib/CodeGen/SelectionDAG/SelectionDAG.cpp b/lib/CodeGen/SelectionDAG/SelectionDAG.cpp index 75cb2c2d06a..91df1ab7b44 100644 --- a/lib/CodeGen/SelectionDAG/SelectionDAG.cpp +++ b/lib/CodeGen/SelectionDAG/SelectionDAG.cpp @@ -807,7 +807,6 @@ void SelectionDAG::init(MachineFunction &mf) { SelectionDAG::~SelectionDAG() { allnodes_clear(); delete Ordering; - DbgInfo->clear(); delete DbgInfo; } @@ -837,8 +836,6 @@ void SelectionDAG::clear() { delete Ordering; Ordering = new SDNodeOrdering(); DbgInfo->clear(); - delete DbgInfo; - DbgInfo = new SDDbgInfo(); } SDValue SelectionDAG::getSExtOrTrunc(SDValue Op, DebugLoc DL, EVT VT) {