From d93459992e559e774e7b14208e5bd8bf27a58280 Mon Sep 17 00:00:00 2001 From: Matt Arsenault Date: Tue, 22 Sep 2020 11:46:41 -0400 Subject: [PATCH] LiveDebugValues: Fix typos and indentation --- llvm/lib/CodeGen/LiveDebugValues/VarLocBasedImpl.cpp | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/llvm/lib/CodeGen/LiveDebugValues/VarLocBasedImpl.cpp b/llvm/lib/CodeGen/LiveDebugValues/VarLocBasedImpl.cpp index 16921ef..8833021 100644 --- a/llvm/lib/CodeGen/LiveDebugValues/VarLocBasedImpl.cpp +++ b/llvm/lib/CodeGen/LiveDebugValues/VarLocBasedImpl.cpp @@ -22,7 +22,7 @@ /// and the VarLocBasedLDV class is an implementation that explicitly tracks /// locations, using the VarLoc class. /// -/// The cannonical "available expressions" problem doesn't have expression +/// The canonical "available expressions" problem doesn't have expression /// clobbering, instead when a variable is re-assigned, any expressions using /// that variable get invalidated. LiveDebugValues can map onto "available /// expressions" by having every register represented by a variable, which is @@ -826,7 +826,7 @@ VarLocBasedLDV::VarLocBasedLDV() { } VarLocBasedLDV::~VarLocBasedLDV() { } /// Erase a variable from the set of open ranges, and additionally erase any -/// fragments that may overlap it. If the VarLoc is a buckup location, erase +/// fragments that may overlap it. If the VarLoc is a backup location, erase /// the variable from the EntryValuesBackupVars set, indicating we should stop /// tracking its backup entry location. Otherwise, if the VarLoc is primary /// location, erase the variable from the Vars set. @@ -1837,8 +1837,8 @@ bool VarLocBasedLDV::ExtendRanges(MachineFunction &MF, TargetPassConfig *TPC) { MachineBasicBlock &First_MBB = *(MF.begin()); for (auto &MI : First_MBB) { collectRegDefs(MI, DefinedRegs, TRI); - if (MI.isDebugValue()) - recordEntryValue(MI, DefinedRegs, OpenRanges, VarLocIDs); + if (MI.isDebugValue()) + recordEntryValue(MI, DefinedRegs, OpenRanges, VarLocIDs); } // Initialize per-block structures and scan for fragment overlaps. -- 2.7.4