[commit: ghc] master: Fix "CPP directive" in comment (d59cf4e)

git at git.haskell.org git at git.haskell.org
Tue Jul 7 09:51:12 UTC 2015


Repository : ssh://git@git.haskell.org/ghc

On branch  : master
Link       : http://ghc.haskell.org/trac/ghc/changeset/d59cf4e503cb5f129b163e1280f5fe4a83e8e4d5/ghc

>---------------------------------------------------------------

commit d59cf4e503cb5f129b163e1280f5fe4a83e8e4d5
Author: Ben Gamari <ben at smart-cactus.org>
Date:   Tue Jul 7 11:50:48 2015 +0200

    Fix "CPP directive" in comment


>---------------------------------------------------------------

d59cf4e503cb5f129b163e1280f5fe4a83e8e4d5
 compiler/codeGen/StgCmmClosure.hs | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/compiler/codeGen/StgCmmClosure.hs b/compiler/codeGen/StgCmmClosure.hs
index 850632c..f8741b7 100644
--- a/compiler/codeGen/StgCmmClosure.hs
+++ b/compiler/codeGen/StgCmmClosure.hs
@@ -778,12 +778,12 @@ Note [Black-holing non-updatable thunks]
 =========================================
 
 We cannot black-hole non-updatable thunks otherwise we run into issues like
-#10414. A single-entry (non-updatable) thunk can actually be entered more than
-once in a parallel program, if work is duplicated by two threads both entering
-the same updatable thunk before the other has blackholed it. So, we must not
-eagerly blackhole non-updatable thunks, or the second thread to enter one will
-become blocked indefinitely. (They are not blackholed by lazy blackholing
-either, since they have no associated update frame.)
+Trac #10414. A single-entry (non-updatable) thunk can actually be entered more
+than once in a parallel program, if work is duplicated by two threads both
+entering the same updatable thunk before the other has blackholed it. So, we
+must not eagerly blackhole non-updatable thunks, or the second thread to enter
+one will become blocked indefinitely. (They are not blackholed by lazy
+blackholing either, since they have no associated update frame.)
 
 For instance, let's consider the following value (in pseudo-Core, example due to
 Reid Barton),



More information about the ghc-commits mailing list