diff options
| author | Ben Gamari <ben@smart-cactus.org> | 2022-01-30 08:45:49 -0500 |
|---|---|---|
| committer | Marge Bot <ben+marge-bot@smart-cactus.org> | 2022-02-01 12:29:26 -0500 |
| commit | 88fba8a4b3c22e953a634b81dd0b67ec66eb5e72 (patch) | |
| tree | 75a46332ad32cfeaf4f4d52b3b60fd452f2493b6 /rts/Capability.c | |
| parent | 06185102bb06d6d56e00d40172a6a473fc228501 (diff) | |
| download | haskell-88fba8a4b3c22e953a634b81dd0b67ec66eb5e72.tar.gz | |
Fix a few Note inconsistencies
Diffstat (limited to 'rts/Capability.c')
| -rw-r--r-- | rts/Capability.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/rts/Capability.c b/rts/Capability.c index 374dfe8de7..7ebe51609f 100644 --- a/rts/Capability.c +++ b/rts/Capability.c @@ -660,7 +660,6 @@ enqueueWorker (Capability* cap USED_IF_THREADS) /* * Note [Benign data race due to work-pushing] * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - * * #17276 points out a tricky data race (noticed by ThreadSanitizer) between * waitForWorkerCapability and schedulePushWork. In short, schedulePushWork * works as follows: @@ -1039,7 +1038,6 @@ yieldCapability /* * Note [migrated bound threads] * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - * * There's a tricky case where: * - cap A is running an unbound thread T1 * - there is a bound thread T2 at the head of the run queue on cap A @@ -1060,7 +1058,6 @@ yieldCapability * * Note [migrated bound threads 2] * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - * * Second tricky case; * - A bound Task becomes a GC thread * - scheduleDoGC() migrates the thread belonging to this Task, |