aboutsummaryrefslogtreecommitdiff
path: root/llvm/unittests/ProfileData/CoverageMappingTest.cpp
diff options
context:
space:
mode:
authorMatt Morehouse <mascasa@google.com>2021-05-14 09:02:49 -0700
committerMatt Morehouse <mascasa@google.com>2021-05-14 09:47:20 -0700
commitb7d1ab75cf474fb3ffc7e7173762c4d83eb2ef8e (patch)
treeca8721cce3684512074dcdbfbda52d36857d2814 /llvm/unittests/ProfileData/CoverageMappingTest.cpp
parent769cc335e6e63e5eac0c0ac849de44714326e20b (diff)
downloadllvm-b7d1ab75cf474fb3ffc7e7173762c4d83eb2ef8e.zip
llvm-b7d1ab75cf474fb3ffc7e7173762c4d83eb2ef8e.tar.gz
llvm-b7d1ab75cf474fb3ffc7e7173762c4d83eb2ef8e.tar.bz2
[HWASan] Add aliasing flag and enable HWASan to use it.
-fsanitize-hwaddress-experimental-aliasing is intended to distinguish aliasing mode from LAM mode on x86_64. check-hwasan is configured to use aliasing mode while check-hwasan-lam is configured to use LAM mode. The current patch doesn't actually do anything differently in the two modes. A subsequent patch will actually build the separate runtimes and use them in each mode. Currently LAM mode tests must be run in an emulator that has LAM support. To ensure LAM mode isn't broken by future patches, I will next set up a QEMU buildbot to run the HWASan tests in LAM. Reviewed By: vitalybuka Differential Revision: https://reviews.llvm.org/D102288
Diffstat (limited to 'llvm/unittests/ProfileData/CoverageMappingTest.cpp')
0 files changed, 0 insertions, 0 deletions