diff options
| author | Thomas Roos <throos@amazon.de> | 2025-01-22 13:44:07 +0100 |
|---|---|---|
| committer | Ross Burton <ross.burton@arm.com> | 2025-01-23 11:56:47 +0000 |
| commit | a58f8a087b8d60cdb3e072233fcc8abd81906c72 (patch) | |
| tree | 0be81bd06d0d837d89d32bff012bfb6d9996e917 /scripts/cve-json-to-text.py | |
| parent | a58e99ce3a5724bec5490b61c48178bdbd4f2ebe (diff) | |
| download | poky-a58f8a087b8d60cdb3e072233fcc8abd81906c72.tar.gz | |
gcc-sanitizers.inc: Workaround for aarch64
When using the -fsanitize=address CXX_FLAG for a program compiled for
aarch64 / arm64
This is happing:
MemorySanitizer: CHECK failed: sanitizer_allocator_primary64.h:133 "((kSpaceBeg))
== ((address_range.Init(TotalSpaceSize, PrimaryAllocatorName, kSpaceBeg)))"
(0xe00000000000, 0xfffffffffffffff4) (tid=51745)
With -DSANITIZER_CAN_USE_ALLOCATOR64=0 this is not happening and
potenial bugs are detected.
ARM32 does not require this patch.
More info about the issue in this thread:
https://github.com/llvm/llvm-project/issues/65144
(From OE-Core rev: 12442b9b6df06317174066854935b1d6a4f1865d)
Signed-off-by: Thomas Roos <throos@amazon.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Diffstat (limited to 'scripts/cve-json-to-text.py')
0 files changed, 0 insertions, 0 deletions