On 08/01/16 04:48, marxin wrote:
Hi.
My attempt in the following small series is to cover couple of issues
I've recently observed. I'll briefly describe changes in respect to
an individual patch:
marxin (4):
Cherry-pick fprofile-generate-atomic from google/gcc-4_9 branch
As mentioned in [1], our current implementation can produce a corrupted
profile due to a massive usage of threads. Well, the absolutely robust
solution would be to either utilize TLS or to use atomics & locking
mechanism. However, as David Li pointed out, the most interesting
counters that can suffer from multithreading are -fprofile-arcs counters
and indirect call counters. I've just cherry picked the functionality
from google/gcc-4_9 branch.
[1] https://gcc.gnu.org/ml/gcc/2016-07/msg00131.html
Remove __gcov_indirect_call_profiler
The profiler function is unused, thus can be removed.
Fix typo in gcov.texi
Just a small typo in names of functions that one can call from
a user application.
Add tests for __gcov_dump and __gcov_reset
Adding tests for the aforementioned functions.
Patches 2,3 & 4 are ok. patch 1 (the fprofile-generate-atomic) needs work.
I'll respond to that one directly.
nathan
