[llvm-bugs] [Bug 44792] Dead lock when forking with coverage enabled in multithreaded environment

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=44792

Hans Wennborg <hans at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #11 from Hans Wennborg <hans at chromium.org> ---
Sounds good to me. On master:

commit 546918cbb4b2231c65cf91fceb738a59d03af7bf
Author: Hans Wennborg <hans at chromium.org>
Date:   Wed Feb 26 13:23:56 2020 +0100

    Revert "[compiler-rt] Add a critical section when flushing gcov counters"

    See discussion on PR44792.

    This reverts commit 02ce9d8ef5a84bc884de4105eae5f8736ef67634.

    It also reverts the follow-up commits
    8f46269f0 "[profile] Don't dump counters when forking and don't reset when
calling exec** functions"
    62c7d8402 "[profile] gcov_mutex must be static"


On 10.x:

commit 57a064f8dc8301ce8b017c84782286816dc58911
Author: Hans Wennborg <hans at chromium.org>
Date:   Wed Feb 26 13:31:58 2020 +0100

    Revert "[compiler-rt] Add a critical section when flushing gcov counters"

    See the discussion on PR44792.

    This reverts commit 02ce9d8ef5a84bc884de4105eae5f8736ef67634.



I believe this gets us back to the state things were in in the 9.x releases.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200226/15110b3d/attachment-0001.html>