diff options
author | Gabor Greif <ggreif@gmail.com> | 2017-07-06 10:48:52 +0200 |
---|---|---|
committer | Gabor Greif <ggreif@gmail.com> | 2017-07-06 10:48:52 +0200 |
commit | 99adcc8804e91161b35ff1d0e5f718d18fcaa66a (patch) | |
tree | e12b65bf767f0f3174fb2df2ceff3fc8a8d34130 /rts | |
parent | f3979b7fbd83e85301ba2f028936fb7c50a48f42 (diff) | |
download | haskell-99adcc8804e91161b35ff1d0e5f718d18fcaa66a.tar.gz |
Typos in comments [ci skip]
Diffstat (limited to 'rts')
-rw-r--r-- | rts/Apply.cmm | 2 | ||||
-rw-r--r-- | rts/PrimOps.cmm | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/rts/Apply.cmm b/rts/Apply.cmm index 36a9859aeb..64f0a9bd54 100644 --- a/rts/Apply.cmm +++ b/rts/Apply.cmm @@ -462,7 +462,7 @@ middle of an ST action multiple times, resulting in duplication of effects. In short, the construction of an AP_STACK allows us to suspend a computation which should not be duplicated. When running with lazy blackholing, we can then enter this AP_STACK multiple times, duplicating the computation with potentially -disasterous consequences. +disastrous consequences. For instance, consider the case of a simple ST program which computes a sum using in─place mutation, diff --git a/rts/PrimOps.cmm b/rts/PrimOps.cmm index 006c9de8c8..3d4bea433d 100644 --- a/rts/PrimOps.cmm +++ b/rts/PrimOps.cmm @@ -148,7 +148,7 @@ stg_isByteArrayPinnedzh ( gcptr ba ) W_ bd, flags; bd = Bdescr(ba); // Pinned byte arrays live in blocks with the BF_PINNED flag set. - // We also consider BF_LARGE objects to be unmoveable. See #13894. + // We also consider BF_LARGE objects to be immovable. See #13894. // See the comment in Storage.c:allocatePinned. flags = TO_W_(bdescr_flags(bd)); return (flags & (BF_PINNED | BF_LARGE) != 0); |