From: Dan Gohman Date: Fri, 25 Jul 2008 15:08:37 +0000 (+0000) Subject: Disable the new aggressive remat logic introduced in 54000; it causes some X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=4c8f87038ddc0fbcce751f0e2e7c0e564abca096;p=oota-llvm.git Disable the new aggressive remat logic introduced in 54000; it causes some regressions, such as PR2595. Also, there is a significant code-quality issue in SPEC 464.h264ref and a few others. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@54014 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/lib/CodeGen/LiveIntervalAnalysis.cpp b/lib/CodeGen/LiveIntervalAnalysis.cpp index adc1e207b50..09557851be4 100644 --- a/lib/CodeGen/LiveIntervalAnalysis.cpp +++ b/lib/CodeGen/LiveIntervalAnalysis.cpp @@ -47,6 +47,8 @@ static cl::opt SplitAtBB("split-intervals-at-bb", static cl::opt SplitLimit("split-limit", cl::init(-1), cl::Hidden); +static cl::opt EnableAggressiveRemat("aggressive-remat", cl::Hidden); + STATISTIC(numIntervals, "Number of original intervals"); STATISTIC(numIntervalsAfter, "Number of intervals after coalescing"); STATISTIC(numFolds , "Number of loads/stores folded into instructions"); @@ -797,6 +799,8 @@ bool LiveIntervals::isReMaterializable(const LiveInterval &li, // rules. if (!MI->getDesc().isRematerializable() || !tii_->isTriviallyReMaterializable(MI)) { + if (!EnableAggressiveRemat) + return false; // If the instruction access memory but the memoperands have been lost, // we can't analyze it.