summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGuillaume Chatelet <gchatelet@google.com>2019-09-06 13:54:09 +0000
committerGuillaume Chatelet <gchatelet@google.com>2019-09-06 13:54:09 +0000
commit5d870c2ec0a631f41ec4387e9d3c6073fea9c178 (patch)
tree176ff8fbd2554f91f0606350560a19a15f95e4db
parent8455294f2ac13d587b13d728038a9bffa7185f2b (diff)
downloadbcm5719-llvm-5d870c2ec0a631f41ec4387e9d3c6073fea9c178.tar.gz
bcm5719-llvm-5d870c2ec0a631f41ec4387e9d3c6073fea9c178.zip
[Alignment] fix dubious min function alignment
Summary: This was discovered while introducing the llvm::Align type. The original setMinFunctionAlignment used to take alignment as log2, looking at the comment it seems like instructions are to be 2-bytes aligned and not 4-bytes aligned. Reviewers: uweigand Subscribers: hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D67271 llvm-svn: 371204
-rw-r--r--llvm/lib/Target/SystemZ/SystemZISelLowering.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/lib/Target/SystemZ/SystemZISelLowering.cpp b/llvm/lib/Target/SystemZ/SystemZISelLowering.cpp
index 5fd4252599c..d4d0905545c 100644
--- a/llvm/lib/Target/SystemZ/SystemZISelLowering.cpp
+++ b/llvm/lib/Target/SystemZ/SystemZISelLowering.cpp
@@ -120,7 +120,7 @@ SystemZTargetLowering::SystemZTargetLowering(const TargetMachine &TM,
setBooleanVectorContents(ZeroOrNegativeOneBooleanContent);
// Instructions are strings of 2-byte aligned 2-byte values.
- setMinFunctionAlignment(llvm::Align(4));
+ setMinFunctionAlignment(llvm::Align(2));
// For performance reasons we prefer 16-byte alignment.
setPrefFunctionLogAlignment(4);
OpenPOWER on IntegriCloud