diff options
| author | Ben Gamari <ben@smart-cactus.org> | 2015-07-07 11:50:48 +0200 |
|---|---|---|
| committer | Ben Gamari <ben@smart-cactus.org> | 2015-07-07 11:51:48 +0200 |
| commit | d59cf4e503cb5f129b163e1280f5fe4a83e8e4d5 (patch) | |
| tree | e28a08fea6440d9925c2b4ef74d9fc9dae50fca4 /compiler/codeGen | |
| parent | d27e7fdb1f16ebb28fee007fc0b1dfbd761789d7 (diff) | |
| download | haskell-d59cf4e503cb5f129b163e1280f5fe4a83e8e4d5.tar.gz | |
Fix "CPP directive" in comment
Diffstat (limited to 'compiler/codeGen')
| -rw-r--r-- | compiler/codeGen/StgCmmClosure.hs | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/compiler/codeGen/StgCmmClosure.hs b/compiler/codeGen/StgCmmClosure.hs index 850632c3b1..f8741b7fb6 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), |