diff options
| author | Arthur Eubanks <aeubanks@google.com> | 2022-08-02 10:43:30 -0700 |
|---|---|---|
| committer | Arthur Eubanks <aeubanks@google.com> | 2022-08-03 17:21:19 -0700 |
| commit | 203296d642c385da07a62098050b08493ed8b236 (patch) | |
| tree | 6151c175afc13aabdd3674c2d91879f687990e82 /llvm/tools/llvm-jitlink/llvm-jitlink.cpp | |
| parent | a2aa6809a8480ae45253613fb081fb138edcd80f (diff) | |
| download | llvm-203296d642c385da07a62098050b08493ed8b236.zip llvm-203296d642c385da07a62098050b08493ed8b236.tar.gz llvm-203296d642c385da07a62098050b08493ed8b236.tar.bz2 | |
[BoundsChecking] Fix merging of sizes
BoundsChecking uses ObjectSizeOffsetEvaluator to keep track of the
underlying size/offset of pointers in allocations. However,
ObjectSizeOffsetVisitor (something ObjectSizeOffsetEvaluator
uses to check for constant sizes/offsets)
doesn't quite treat sizes and offsets the same way as
BoundsChecking. BoundsChecking wants to know the size of the
underlying allocation and the current pointer's offset within
it, but ObjectSizeOffsetVisitor only cares about the size
from the pointer to the end of the underlying allocation.
This only comes up when merging two size/offset pairs. Add a new mode to
ObjectSizeOffsetVisitor which cares about the underlying size/offset
rather than the size from the current pointer to the end of the
allocation.
Fixes a false positive with -fsanitize=bounds.
Reviewed By: vitalybuka, asbirlea
Differential Revision: https://reviews.llvm.org/D131001
Diffstat (limited to 'llvm/tools/llvm-jitlink/llvm-jitlink.cpp')
0 files changed, 0 insertions, 0 deletions