summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Gamari <ben@smart-cactus.org>2017-07-04 16:45:30 (GMT)
committerBen Gamari <ben@smart-cactus.org>2017-07-05 18:49:07 (GMT)
commit555e5cc48b6c2608ae8d4bd3b2a5bd2ef63236ab (patch)
tree32df1ea767371f245dc31684ca8d4c2be977ae0e
parent3eeb55e9578f6eaebccf27170eb1324990affb51 (diff)
downloadghc-555e5cc48b6c2608ae8d4bd3b2a5bd2ef63236ab.zip
ghc-555e5cc48b6c2608ae8d4bd3b2a5bd2ef63236ab.tar.gz
ghc-555e5cc48b6c2608ae8d4bd3b2a5bd2ef63236ab.tar.bz2
rts: Address AP_STACK comment suggestion from Simon
-rw-r--r--rts/Apply.cmm6
1 files changed, 3 insertions, 3 deletions
diff --git a/rts/Apply.cmm b/rts/Apply.cmm
index a0b498a..36a9859 100644
--- a/rts/Apply.cmm
+++ b/rts/Apply.cmm
@@ -506,9 +506,9 @@ Here we have two threads (TSO 1 and TSO 2) which are in currently pausing (e.g.
in threadPaused). Since they are pausing, their stacks are headed by a pointer
to the continuation code which we will run on resumption (go and fun,
respectively). We also see that there are two thunks on the heap: THUNK A and
-THUNK B where THUNK A is reachable from THUNK B (for instance, as an argument or
-free variable). We see that thread 1 has THUNK A under evaluation, and both
-threads have THUNK B under evaluation.
+THUNK B where THUNK B depends upon THUNK A (as in, evaluation of B will force
+A). We see that thread 1 has THUNK A under evaluation, and both threads have
+THUNK B under evaluation.
As each thread enters threadPaused, threadPaused will walk its stack looking for
duplicate computation (see Note [suspend duplicate work], although there is some