From d462f1ae708ec8b8f7d280a4a32a11d9d983d20d Mon Sep 17 00:00:00 2001 From: Jessica Paquette Date: Mon, 20 Mar 2017 15:51:45 +0000 Subject: [PATCH] [Outliner] Remove output for offset range check Forgot to remove some output before committing last time. (Instruction fixups don't actually overflow anywhere in the test suite so far, so I missed it). To prevent the outliner from screaming "Overflow!" in the event that that does happen, this commit removes that output. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@298260 91177308-0d34-0410-b5e6-96231b3b80d8 --- lib/Target/AArch64/AArch64InstrInfo.cpp | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/lib/Target/AArch64/AArch64InstrInfo.cpp b/lib/Target/AArch64/AArch64InstrInfo.cpp index 308f9da5cd3..19d54904d4e 100644 --- a/lib/Target/AArch64/AArch64InstrInfo.cpp +++ b/lib/Target/AArch64/AArch64InstrInfo.cpp @@ -4348,10 +4348,8 @@ AArch64InstrInfo::getOutliningType(MachineInstr &MI) const { // TODO: We should really test what happens if an instruction overflows. // This is tricky to test with IR tests, but when the outliner is moved // to a MIR test, it really ought to be checked. - if (Offset + 16 < MinOffset || Offset + 16 > MaxOffset) { + if (Offset + 16 < MinOffset || Offset + 16 > MaxOffset) errs() << "Overflow!\n"; - return MachineOutlinerInstrType::Illegal; - } // It's in range, so we can outline it. return MachineOutlinerInstrType::Legal; -- 2.40.0