aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/MetadataLoader.cpp
diff options
context:
space:
mode:
authorNagyDonat <donat.nagy@ericsson.com>2024-03-19 14:12:27 +0100
committerGitHub <noreply@github.com>2024-03-19 14:12:27 +0100
commit175ad6630a869831126dde80f0f9257f9c4c477f (patch)
tree4a4381e7e190cce79840afde8d27e708fcc3d8b3 /llvm/lib/Bitcode/Reader/MetadataLoader.cpp
parent335f3659820e2e771f5165d215300567be478b13 (diff)
downloadllvm-175ad6630a869831126dde80f0f9257f9c4c477f.zip
llvm-175ad6630a869831126dde80f0f9257f9c4c477f.tar.gz
llvm-175ad6630a869831126dde80f0f9257f9c4c477f.tar.bz2
[analyzer] Mention possibility of underflow in array overflow errors (#84201)
The checker alpha.security.ArrayBoundV2 performs bounds checking in two steps: first it checks for underflow, and if it isn't guaranteed then it assumes that there is no underflow. After this, it checks for overflow, and if that's guaranteed or the index is tainted then it reports it. This meant that in situations where overflow and underflow are both possible (but the index is either tainted or guaranteed to be invalid), the checker was reporting just an overflow error. This commit modifies the messages printed in these cases to mention the possibility of an underflow. --------- Co-authored-by: Balazs Benics <benicsbalazs@gmail.com>
Diffstat (limited to 'llvm/lib/Bitcode/Reader/MetadataLoader.cpp')
0 files changed, 0 insertions, 0 deletions