summaryrefslogtreecommitdiff
path: root/rts/sm/Storage.c
diff options
context:
space:
mode:
authorGabor Greif <ggreif@gmail.com>2017-09-25 12:31:12 +0200
committerGabor Greif <ggreif@gmail.com>2017-09-26 11:13:14 +0200
commit7446c7f68bd5addd2f2db0d8d5910fb963869c47 (patch)
tree05ecf5d25cdecb2893424cd07b0e7002b32ea2c4 /rts/sm/Storage.c
parent2f8e6e7f8696213b95e3461224909c3b2ec4f7aa (diff)
downloadhaskell-7446c7f68bd5addd2f2db0d8d5910fb963869c47.tar.gz
A bunch of typofixes
Diffstat (limited to 'rts/sm/Storage.c')
-rw-r--r--rts/sm/Storage.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/rts/sm/Storage.c b/rts/sm/Storage.c
index ffaed5f17c..6c5a73310c 100644
--- a/rts/sm/Storage.c
+++ b/rts/sm/Storage.c
@@ -315,7 +315,7 @@ freeStorage (bool free_heap)
- pushes an update frame pointing to the CAF_BLACKHOLE
- Why do we build an BLACKHOLE in the heap rather than just updating
+ Why do we build a BLACKHOLE in the heap rather than just updating
the thunk directly? It's so that we only need one kind of update
frame - otherwise we'd need a static version of the update frame
too, and various other parts of the RTS that deal with update