diff options
| author | Roman Lebedev <lebedev.ri@gmail.com> | 2019-12-03 17:45:47 +0300 |
|---|---|---|
| committer | Roman Lebedev <lebedev.ri@gmail.com> | 2019-12-03 20:04:51 +0300 |
| commit | 9a20c79ddc2523fb68be4d4246d7835c761c382f (patch) | |
| tree | 064eab89c1f5fe78847c52311ad22de67a89b054 /llvm/utils/FileCheck/FileCheck.cpp | |
| parent | 372ad32734ecb455f9fb4d0601229ca2dfc78b66 (diff) | |
| download | llvm-9a20c79ddc2523fb68be4d4246d7835c761c382f.zip llvm-9a20c79ddc2523fb68be4d4246d7835c761c382f.tar.gz llvm-9a20c79ddc2523fb68be4d4246d7835c761c382f.tar.bz2 | |
[NFC][KnownBits] Add getMinValue() / getMaxValue() methods
As it can be seen from accompanying cleanup, it is not unheard of
to write `~Known.Zero` meaning "what maximal value can this KnownBits
produce". But i think `~Known.Zero` isn't *that* self-explanatory,
as compared to a method with a name.
Note that not all `~Known.Zero` places were cleaned up,
only those where this arguably improves things.
Diffstat (limited to 'llvm/utils/FileCheck/FileCheck.cpp')
0 files changed, 0 insertions, 0 deletions