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

cs: avoid promoting unknown OS thread to known

Browse Source 
Related to changes in 18a95c3ae6, but shouldn't affect the problem
that commit addressed, since Racket-level callbacks need to be
involved.
This commit is contained in:
Matthew Flatt 2021-06-01 10:32:36 -06:00
parent a531efe0d5
commit 9736595c7b
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
racket/src/cs/rumble/foreign.ss
View File

@ -1768,7 +1768,7 @@
(loop (cdr types) (cons (ctype-host-rep type) reps) decls)))]))) (loop (cdr types) (cons (ctype-host-rep type) reps) decls)))])))
;; Rely on the fact that a virtual register defaults to 0 to detect a ;; Rely on the fact that a virtual register defaults to 0 to detect a
;; thread that we didn't start. For a thread that we did start, a ;; thread that we didn't start.
(define PLACE-UNKNOWN-THREAD 0) (define PLACE-UNKNOWN-THREAD 0)
(define PLACE-KNOWN-THREAD 1) (define PLACE-KNOWN-THREAD 1)
(define PLACE-MAIN-THREAD 2) (define PLACE-MAIN-THREAD 2)

4
racket/src/cs/rumble/virtual-register.ss
View File

@ -44,4 +44,6 @@
;; foreign thread that has not yet been initialized to run Rumble ;; foreign thread that has not yet been initialized to run Rumble
;; and later layers: ;; and later layers:
(when (eq? 0 (current-future)) (when (eq? 0 (current-future))
(init-virtual-registers))) (init-virtual-registers)
;; set `place-thread-category` back to "unknown":
(place-thread-category PLACE-UNKNOWN-THREAD)))