Before the change, DFSan always does the propagation. W/o
origin tracking, it is harder to understand such flows. After
the change, the flag is off by default.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Time | Test | |
---|---|---|
380 ms | linux > HWAddressSanitizer-x86_64.TestCases::sizes.cpp |
Event Timeline
llvm/lib/Transforms/Instrumentation/DataFlowSanitizer.cpp | ||
---|---|---|
191 | It only applies to selects, so maybe we should name it something like dfsan-track-select-control-flow. and update the description/comment. | |
193 | This changes the default behavior. Does it cause any existing tests to fail? Maybe we should default it to true. | |
llvm/test/Instrumentation/DataFlowSanitizer/select.ll | ||
51 | I think this tests the same case as select8. If we want to test the vector one, we need %c to be a vector. |
It only applies to selects, so maybe we should name it something like dfsan-track-select-control-flow. and update the description/comment.