From 594e2aa61eaba17d9836551ca479d987f2d9e059 Mon Sep 17 00:00:00 2001 From: Andrew Trick Date: Thu, 27 Feb 2014 21:37:30 +0000 Subject: [PATCH] Drive-by comment fix. This regalloc comment was not accurate. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@202432 91177308-0d34-0410-b5e6-96231b3b80d8 --- include/llvm/Target/TargetRegisterInfo.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/include/llvm/Target/TargetRegisterInfo.h b/include/llvm/Target/TargetRegisterInfo.h index 5f50e402b9c..22a2bde9cb4 100644 --- a/include/llvm/Target/TargetRegisterInfo.h +++ b/include/llvm/Target/TargetRegisterInfo.h @@ -675,12 +675,12 @@ public: /// Allow the target to reverse allocation order of local live ranges. This /// will generally allocate shorter local live ranges first. For targets with /// many registers, this could reduce regalloc compile time by a large - /// factor. It should still achieve optimal coloring; however, it can change - /// register eviction decisions. It is disabled by default for two reasons: + /// factor. It is disabled by default for three reasons: /// (1) Top-down allocation is simpler and easier to debug for targets that /// don't benefit from reversing the order. /// (2) Bottom-up allocation could result in poor evicition decisions on some /// targets affecting the performance of compiled code. + /// (3) Bottom-up allocation is no longer guaranteed to optimally color. virtual bool reverseLocalAssignment() const { return false; } /// requiresRegisterScavenging - returns true if the target requires (and can -- 2.11.0