aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Serialization/ModuleCache.cpp
diff options
context:
space:
mode:
authorThurston Dang <thurston@google.com>2025-10-14 22:48:04 +0000
committerGitHub <noreply@github.com>2025-10-14 15:48:04 -0700
commit6ae457d0b2f5efa7032406239bd0684016c30d7b (patch)
tree0df5682ca3973d0bb0e382caa42ddfc687da4348 /clang/lib/Serialization/ModuleCache.cpp
parent19a58a520820a0678e767abdf418f101cfd5ca1a (diff)
downloadllvm-6ae457d0b2f5efa7032406239bd0684016c30d7b.zip
llvm-6ae457d0b2f5efa7032406239bd0684016c30d7b.tar.gz
llvm-6ae457d0b2f5efa7032406239bd0684016c30d7b.tar.bz2
[msan] Mark allocator padding as uninitialized, with new origin tag (#157187)
This is follow-up work per discussion in https://github.com/llvm/llvm-project/pull/155944#discussion_r2311688571. If the allocator reserves more space than the user requested (e.g., `malloc(7)` and `calloc(7,1)` actually have 16 bytes reserved), the padding bytes will now be marked as uninitialized. Padding poisoning is controlled by the existing flag `poison_in_malloc` (which applies to all allocation functions, not only malloc). Origin tag: - For `calloc` or with track-origins > 1, the origin will be set as a new tag, `ALLOC_PADDING` - Otherwise, the existing `ALLOC` tag will be used. - In the case of ambiguity caused by origin granularity, `ALLOC` will take precedence.
Diffstat (limited to 'clang/lib/Serialization/ModuleCache.cpp')
0 files changed, 0 insertions, 0 deletions