This allows application code checks if origin tracking is on before
printing out traces.
-dfsan-track-origins can be 0,1,2.
The current code only distinguishes 1 and 2 in compile time, but not at runtime.
Made runtime distinguish 1 and 2 too.
Paths
| Differential D105128
[dfsan] Expose dfsan_get_track_origins to get origin tracking status ClosedPublic Authored by stephan.yichao.zhao on Jun 29 2021, 8:35 AM.
Details Summary This allows application code checks if origin tracking is on before -dfsan-track-origins can be 0,1,2.
Diff Detail
Event TimelineHerald added projects: Restricted Project, Restricted Project. · View Herald TranscriptJun 29 2021, 8:35 AM
stephan.yichao.zhao marked an inline comment as done. Comment ActionsAdded more comments to dfsan_get_track_origins.
This revision is now accepted and ready to land.Jun 29 2021, 1:29 PM Closed by commit rGae6648cee01b: [dfsan] Expose dfsan_get_track_origins to get origin tracking status (authored by Jianzhou Zhao <jianzhouzh@google.com>). · Explain WhyJun 29 2021, 1:33 PM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 355273 compiler-rt/include/sanitizer/dfsan_interface.h
compiler-rt/lib/dfsan/dfsan.cpp
compiler-rt/lib/dfsan/done_abilist.txt
compiler-rt/test/dfsan/dfsan_get_track_origins.c
llvm/lib/Transforms/Instrumentation/DataFlowSanitizer.cpp
llvm/test/Instrumentation/DataFlowSanitizer/basic.ll
|
Comment here should explain the meaning of different return values, or link to something that does.