summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJessica Paquette <jpaquette@apple.com>2017-03-20 15:51:45 +0000
committerJessica Paquette <jpaquette@apple.com>2017-03-20 15:51:45 +0000
commit5d59a4ee19cfe1580932fb5315c1bad5cb8ef767 (patch)
tree091536952b4f65219c60d8b6e88c46728b09526c
parent0d10696693f13c16f2cd7875b5762c124104401c (diff)
downloadbcm5719-llvm-5d59a4ee19cfe1580932fb5315c1bad5cb8ef767.tar.gz
bcm5719-llvm-5d59a4ee19cfe1580932fb5315c1bad5cb8ef767.zip
[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. llvm-svn: 298260
-rw-r--r--llvm/lib/Target/AArch64/AArch64InstrInfo.cpp4
1 files changed, 1 insertions, 3 deletions
diff --git a/llvm/lib/Target/AArch64/AArch64InstrInfo.cpp b/llvm/lib/Target/AArch64/AArch64InstrInfo.cpp
index 308f9da5cd3..19d54904d4e 100644
--- a/llvm/lib/Target/AArch64/AArch64InstrInfo.cpp
+++ b/llvm/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;
OpenPOWER on IntegriCloud