This is patch is part of a series to introduce an Alignment type.
See this thread for context: http://lists.llvm.org/pipermail/llvm-dev/2019-July/133851.html
See this patch for the introduction of the type: https://reviews.llvm.org/D64790
Details
- Reviewers
courbet - Commits
- rG3ba550a05afa: [Alignment][NFC] Use TFL::getStackAlign()
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/Target/X86/X86InstrInfo.cpp | ||
---|---|---|
5376 | Documentation here is useful to understand why this is correct. |
[Alignment][NFC] Use TFL::getStackAlign()
Suggest: TFL -> TargetFrameLowering. Abbreviations on the title line can only cause confusion.
llvm/lib/CodeGen/PrologEpilogInserter.cpp | ||
---|---|---|
442 | inline this on the line below ? Alignment = std::min(Alignment, TFI->getStackAlign()); | |
llvm/lib/CodeGen/SelectionDAG/FunctionLoweringInfo.cpp | ||
132 | const, to make it clear that this does not change in the loop ? | |
llvm/lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp | ||
4031 | I think it was clearer with this conditional here rather than inline later. | |
4037 | extract StackAlign.value() - 1 to a StackAlignMask variable for semantics ? Or maybe even add a getMask() method to llvm::Align given that this is a very common operation ? | |
llvm/lib/Target/PowerPC/PPCRegisterInfo.cpp | ||
548 | would be useful here too. | |
573 | and here |
llvm/lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp | ||
---|---|---|
4031 | Unfortunately if I do so I have to use a MaybeAlign instead of Align to express the 0 case. | |
4037 | I plan to do so as a separate step, maybe introducing a Mask type. There are less cases than it seems though so I'm still weighing the costs / benefits. | |
llvm/lib/Target/PowerPC/PPCRegisterInfo.cpp | ||
548 | Acknowledged |
llvm/lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp | ||
---|---|---|
4031 | I think so. |
inline this on the line below ?
Alignment = std::min(Alignment, TFI->getStackAlign());