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 bollu jdoerfert - Commits
- rGd400d4515053: [Alignment][NFC] Remove StoreInst::setAlignment(unsigned)
rPLO373595: [Alignment][NFC] Remove StoreInst::setAlignment(unsigned)
rC373595: [Alignment][NFC] Remove StoreInst::setAlignment(unsigned)
rL373595: [Alignment][NFC] Remove StoreInst::setAlignment(unsigned)
Diff Detail
- Repository
- rG LLVM Github Monorepo
- Build Status
Buildable 38942 Build 38941: arc lint + arc unit
Event Timeline
| llvm/lib/Transforms/InstCombine/InstCombineCalls.cpp | ||
|---|---|---|
| 189 | FIXME | |
| 203 | ditto | |
| 274 | make it const + remove assert ? | |
| llvm/lib/Transforms/InstCombine/InstCombineLoadStoreAlloca.cpp | ||
| 1367 | getOrEnforceKnownAlignment() seems to always be returning >0 | |
| llvm/lib/Transforms/Vectorize/SLPVectorizer.cpp | ||
| 4027 | I don't think there are any guarantees that getABITypeAlignment is non-zero for now. | |
| llvm/lib/Transforms/Vectorize/SLPVectorizer.cpp | ||
|---|---|---|
| 4027 | Actually it is guaranteed to be an Align. | |
FIXME