aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/StaticAnalyzer/Checkers/StdLibraryFunctionsChecker.cpp
diff options
context:
space:
mode:
authorNikita Popov <npopov@redhat.com>2023-05-16 10:55:44 +0200
committerNikita Popov <npopov@redhat.com>2023-06-01 09:46:16 +0200
commitdfb369399d2a54c8dd8752c47ecbf7a8c3c11421 (patch)
treecc57457a7c2fef38895c4363bf46376c117c8dac /clang/lib/StaticAnalyzer/Checkers/StdLibraryFunctionsChecker.cpp
parent34cf67aef5a3655b57e52842a1bb4913295076e4 (diff)
downloadllvm-dfb369399d2a54c8dd8752c47ecbf7a8c3c11421.zip
llvm-dfb369399d2a54c8dd8752c47ecbf7a8c3c11421.tar.gz
llvm-dfb369399d2a54c8dd8752c47ecbf7a8c3c11421.tar.bz2
[ValueTracking] Directly use KnownBits shift functions
Make ValueTracking directly call the KnownBits shift helpers, which provides more precise results. Unfortunately, ValueTracking has a special case where sometimes we determine non-zero shift amounts using isKnownNonZero(). I have my doubts about the usefulness of that special-case (it is only tested in a single unit test), but I've reproduced the special-case via an extra parameter to the KnownBits methods. Differential Revision: https://reviews.llvm.org/D151816
Diffstat (limited to 'clang/lib/StaticAnalyzer/Checkers/StdLibraryFunctionsChecker.cpp')
0 files changed, 0 insertions, 0 deletions