diff options
| author | Guillaume Chatelet <gchatelet@google.com> | 2020-04-06 10:53:56 +0000 |
|---|---|---|
| committer | Guillaume Chatelet <gchatelet@google.com> | 2020-04-06 14:54:57 +0000 |
| commit | 808286342a6f1c132a655e8dc2477bfb01ecb63a (patch) | |
| tree | b76f9be813fcf1d12567b94c5654d5861acba2dc /lldb/test/API/python_api/default-constructor/TestDefaultConstructorForAPIObjects.py | |
| parent | 2e1afe5232674cab6edf1efefd0c8c88fb63a594 (diff) | |
[Alignment][NFC] Assume AlignmentFromAssumptions::getNewAlignment is always set.
Summary:
In D77454 we explain that `LoadInst` and `StoreInst` always have their alignment defined.
This allows to work backward here and to infer that `getNewAlignment` does not need to return `0` in case of failure.
Returning `1` also works since it needs to be greater than the Load/Store alignment which is a least `1`.
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
Reviewers: courbet
Subscribers: hiraditya, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D77538
Diffstat (limited to 'lldb/test/API/python_api/default-constructor/TestDefaultConstructorForAPIObjects.py')
0 files changed, 0 insertions, 0 deletions