Displaying 3 results from an estimated 3 matches for "__tsan_".
Did you mean:
__tsan
2017 Jul 10
4
Using TSAN along with custom llvm IR pass
...gt; any TSAN warnings!
Hi Nischai,
I see 3 possibilities:
1. Either the code is somehow ends up being non-instrumented, or
2. tsan does not consider what it sees a data race, or
3. the data race is masked by unrelated synchronization.
For 1 you can check that the resulting code in fact contains __tsan_* callbacks.
For 2 and 3 you can rebuilt tsan runtime with TSAN_DEBUG_OUTPUT=2
define, then it will print everything it sees (memory accesses and
synchronization). This output will allow us to figure out why it does
not report a race.
2017 Jul 10
1
Using TSAN along with custom llvm IR pass
...>
> I see 3 possibilities:
> 1. Either the code is somehow ends up being non-instrumented, or
> 2. tsan does not consider what it sees a data race, or
> 3. the data race is masked by unrelated synchronization.
>
> For 1 you can check that the resulting code in fact contains __tsan_*
> callbacks.
> For 2 and 3 you can rebuilt tsan runtime with TSAN_DEBUG_OUTPUT=2
> define, then it will print everything it sees (memory accesses and
> synchronization). This output will allow us to figure out why it does
> not report a race.
>
-------------- next part ----...
2017 Jun 28
1
Using TSAN along with custom llvm IR pass
...itize=thread and -emit-llvm to get the
>> byte code of the file
>> 2. Used opt to run my custom pass on the TSAN instrumented .bc file
>> 3. Run the final .bc file using lli with proper inputs
>>
>> This gives me a "LLVM ERROR: Program used external function '__tsan_init'
>> which could not be resolved!"
Hi,
I don't know what is lli, but from the error message it seems that the
problem is that you don't link in tsan runtime (tsan runtime provides
__tsan_init function).
I think you need to compile you instrumented file into object file...