Displaying 3 results from an estimated 3 matches for "finstr".
Did you mean:
instr
2014 Feb 19
2
[LLVMdev] asan coverage
On Tue, Feb 18, 2014 at 10:15 PM, Bob Wilson <bob.wilson at apple.com> wrote:
> Our instrumentation code is basically done now, so you can try it out and
> compare the performance. Just build with -finstr-profile-generate.
>
Is this in trunk?
clang-3.5: error: unknown argument: '-finstr-profile-generate'
--kcc
> You may want to hack the compiler-rt code in lib/profile/PGOProfiling.c to
> disable writing the output, since the current implementation is pretty
> naive.
>
>...
2014 Feb 18
2
[LLVMdev] asan coverage
Regarding performance, I've made a simple coverage with counters and
compared it with AsanCoverage.
AsanCoverage produces code like this:
mov 0xe86cce(%rip),%al
test %al,%al
je 48b4a0 # to call __sanitizer_cov
...
callq 4715b0 <__sanitizer_cov>
A simple counter-based thing (which just increments counters and does
nothing else useful) produces this:
incq 0xe719c6(%rip)
The
2014 Feb 19
2
[LLVMdev] asan coverage
...at google.com> wrote:
>
>>
>>
>>
>> On Tue, Feb 18, 2014 at 10:15 PM, Bob Wilson <bob.wilson at apple.com>wrote:
>>
>>> Our instrumentation code is basically done now, so you can try it out
>>> and compare the performance. Just build with -finstr-profile-generate.
>>>
>>
>> Is this in trunk?
>> clang-3.5: error: unknown argument: '-finstr-profile-generate'
>>
>> --kcc
>>
>>
>>> You may want to hack the compiler-rt code in lib/profile/PGOProfiling.c
>>> to disable w...