forked from OSchip/llvm-project
Leftover bits from https://reviews.llvm.org/D53420 that were accidentally left
out of revision 344883 llvm-svn: 345021
This commit is contained in:
parent
7189112951
commit
da5dc13355
|
@ -310,9 +310,9 @@ public:
|
|||
|
||||
/// Returns true if this Group requires a scalar iteration to handle gaps.
|
||||
bool requiresScalarEpilogue() const {
|
||||
// If Group has no gaps, or has gaps but the last member exists, then a
|
||||
// scalar epilog is not needed for this group.
|
||||
if (getNumMembers() == getFactor() || getMember(getFactor() - 1))
|
||||
// If the last member of the Group exists, then a scalar epilog is not
|
||||
// needed for this group.
|
||||
if (getMember(getFactor() - 1))
|
||||
return false;
|
||||
|
||||
// We have a group with gaps. It therefore cannot be a group of stores,
|
||||
|
|
|
@ -4600,8 +4600,7 @@ Optional<unsigned> LoopVectorizationCostModel::computeMaxVF(bool OptForSize) {
|
|||
}
|
||||
|
||||
// Record that scalar epilogue is not allowed.
|
||||
LLVM_DEBUG(dbgs() << "LV: Not inserting scalar epilogue for access with gaps "
|
||||
"due to -Os/-Oz.\n");
|
||||
LLVM_DEBUG(dbgs() << "LV: Not allowing scalar epilogue due to -Os/-Oz.\n");
|
||||
|
||||
// We don't create an epilogue when optimizing for size.
|
||||
// Invalidate interleave groups that require an epilogue.
|
||||
|
|
Loading…
Reference in New Issue