diff options
author | Tacet <advenam.tacet@trailofbits.com> | 2024-01-25 20:41:38 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-01-25 20:41:38 +0100 |
commit | a315fb1c577a40a40968daa9d346435458d7e06e (patch) | |
tree | f740fa221b4692a55ff1325dd5a520ae2403e758 /llvm/tools/llvm-objdump/llvm-objdump.cpp | |
parent | a7759fb0f8ce28a53a38a6e0ba6b7105f3d6781a (diff) | |
download | llvm-a315fb1c577a40a40968daa9d346435458d7e06e.zip llvm-a315fb1c577a40a40968daa9d346435458d7e06e.tar.gz llvm-a315fb1c577a40a40968daa9d346435458d7e06e.tar.bz2 |
[ASan][libc++] Correct (explicit) annotation size (#79292)
A quick examination suggests that the current code in the codebase does
not lead to incorrect annotations. However, the intention is for the
object after the function to be annotated in a way that only its
contents are unpoisoned and the rest is poisoned. This commit makes it
explicit and avoids potential issues in future.
In addition, I have implemented a few tests for a function that helped
me identify the specific argument value.
Notice: there is no known scenario where old code results in incorrect
annotation.
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.cpp')
0 files changed, 0 insertions, 0 deletions