aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp
diff options
context:
space:
mode:
authorDaniel Neilson <dneilson@azul.com>2017-07-18 01:06:52 +0000
committerDaniel Neilson <dneilson@azul.com>2017-07-18 01:06:52 +0000
commit92be70f510bbe9e06bc9871f5479607bbfe25dd6 (patch)
tree9286620a404f8402c6ce7bdca5f6cb301fb2a95f /clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp
parent5fc2ee7fabef3f7d1703f852666262d64e2be51b (diff)
downloadllvm-92be70f510bbe9e06bc9871f5479607bbfe25dd6.zip
llvm-92be70f510bbe9e06bc9871f5479607bbfe25dd6.tar.gz
llvm-92be70f510bbe9e06bc9871f5479607bbfe25dd6.tar.bz2
Add element-atomic mem intrinsic canary tests for Dataflow Sanitizer.
Summary: Add canary tests to verify that DFSAN currently does nothing with the element atomic memory intrinsics for memcpy, memmove, and memset. Placeholder tests that will fail once @llvm.mem[cpy|move|set] instrinsics have been added to the MemIntrinsic class hierarchy. These will act as a reminder to verify that DFSAN handles these intrinsics properly once they have been added to that class hierarchy. Note that there could be some trickiness with these element-atomic intrinsics for the dataflow sanitizer in racy multithreaded programs. The data flow sanitizer inserts additional lib calls to mirror the memory intrinsic's action, so it is possible (very likely, even) that the dfsan buffers will not be in sync with the original buffers. Furthermore, implementation of the dfsan buffer updates for the element atomic intrinsics will have to also use unordered atomic instructions. If we can assume that dfsan is never run on racy multithreaded programs, then the element atomic memory intrinsics can pretty much be treated the same as the regular memory intrinsics. Reviewers: reames Reviewed By: reames Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D35507 llvm-svn: 308249
Diffstat (limited to 'clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions