summaryrefslogtreecommitdiffstats
path: root/llvm/unittests/CodeGen/MachineOperandTest.cpp
diff options
context:
space:
mode:
authorAlexander Potapenko <glider@google.com>2017-08-10 15:00:13 +0000
committerAlexander Potapenko <glider@google.com>2017-08-10 15:00:13 +0000
commit5241081532ccc318579958ce9b7bed25e5ed9a45 (patch)
tree338b8f77df74fb9d8a035fa137bb4d56efe8f1f8 /llvm/unittests/CodeGen/MachineOperandTest.cpp
parentc3bcdc2f1a2c2e5476059870ba570987d15c3fe2 (diff)
downloadbcm5719-llvm-5241081532ccc318579958ce9b7bed25e5ed9a45.tar.gz
bcm5719-llvm-5241081532ccc318579958ce9b7bed25e5ed9a45.zip
[sanitizer-coverage] Change cmp instrumentation to distinguish const operands
This implementation of SanitizerCoverage instrumentation inserts different callbacks depending on constantness of operands: 1. If both operands are non-const, then a usual __sanitizer_cov_trace_cmp[1248] call is inserted. 2. If exactly one operand is const, then a __sanitizer_cov_trace_const_cmp[1248] call is inserted. The first argument of the call is always the constant one. 3. If both operands are const, then no callback is inserted. This separation comes useful in fuzzing when tasks like "find one operand of the comparison in input arguments and replace it with the other one" have to be done. The new instrumentation allows us to not waste time on searching the constant operands in the input. Patch by Victor Chibotaru. llvm-svn: 310600
Diffstat (limited to 'llvm/unittests/CodeGen/MachineOperandTest.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud