Re: [GHC] #16150: Data races in itimer_thread_func reported by ThreadSanitizer

17 Jan 2019

      #16150: Data races in itimer_thread_func reported by ThreadSanitizer
-------------------------------------+-------------------------------------
        Reporter:  gnezdo            |                Owner:  (none)
            Type:  bug               |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  Runtime System    |              Version:  8.4.4
      Resolution:                    |             Keywords:
Operating System:  Linux             |         Architecture:  x86_64
 Type of failure:  Incorrect result  |  (amd64)
  at runtime                         |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by Ben Gamari ):

 In [changeset:"ce11f6f25c1160262830d9670c4eaaebac37cbaf/ghc" ce11f6f/ghc]:
 {{{
 #!CommitTicketReference repository="ghc"
 revision="ce11f6f25c1160262830d9670c4eaaebac37cbaf"
 rts: Use always-available locking operations in pthread Itimer
 implementation

 Previously we ACQUIRE_LOCK and RELEASE_LOCK but these compile to a noop in
 the
 non-threaded RTS, as noted in #16150. Use OS_ACQUIRE_LOCK and
 OS_RELEASE_LOCK
 instead.
 }}}

-- 
Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/16150#comment:5
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler