suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

cs: fix future-thread signaling

Browse Source 
Fix confusion between signal and broadcast operation.
This commit is contained in:
Matthew Flatt 2019-06-24 20:14:15 -06:00
parent b64e17388f
commit 3fb226ce2a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
racket/src/thread/future.rkt
View File

@ -407,7 +407,7 @@
(host:mutex-acquire (scheduler-mutex s))
(for ([w (in-list (scheduler-workers s))])
(set-worker-die?! w #t))
(host:condition-signal (scheduler-cond s))
(host:condition-broadcast (scheduler-cond s))
(host:mutex-release (scheduler-mutex s))
(futures-sync-for-shutdown)
(current-scheduler #f)))
@ -423,8 +423,7 @@
(cond
[(not old)
(set-scheduler-futures-head! s f)
(set-scheduler-futures-tail! s f)
(host:condition-signal (scheduler-cond s))]
(set-scheduler-futures-tail! s f)]
[front?
(set-future*-next! f old)
(set-future*-prev! old f)
@ -433,6 +432,7 @@
(set-future*-prev! f old)
(set-future*-next! old f)
(set-scheduler-futures-tail! s f)])
(host:condition-signal (scheduler-cond s))
(host:mutex-release (scheduler-mutex s)))
;; called with queue lock held