Skip to content

Commit

Permalink
Give WHITEHOLE the BLACKHOLE closure type, instead of INVALID_OBJECT
Browse files Browse the repository at this point in the history
Just to keep sanity checking happy, and so we don't need a completely
new closure type.
  • Loading branch information
Simon Marlow committed Mar 10, 2006
1 parent 50bc398 commit 4cb89d6
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion ghc/rts/StgMiscClosures.cmm
Expand Up @@ -435,9 +435,13 @@ INFO_TABLE(stg_SE_CAF_BLACKHOLE,0,1,SE_CAF_BLACKHOLE,"SE_CAF_BLACKHOLE","SE_CAF_
#endif

/* ----------------------------------------------------------------------------
Whiteholes are used for the "locked" state of a closure (see lockClosure())

The closure type is BLAKCHOLE, just because we need a valid closure type
for sanity checking.
------------------------------------------------------------------------- */

INFO_TABLE(stg_WHITEHOLE, 0,0, INVALID_OBJECT, "WHITEHOLE", "WHITEHOLE")
INFO_TABLE(stg_WHITEHOLE, 0,0, BLACKHOLE, "WHITEHOLE", "WHITEHOLE")
{ foreign "C" barf("WHITEHOLE object entered!"); }

/* ----------------------------------------------------------------------------
Expand Down

0 comments on commit 4cb89d6

Please sign in to comment.