Give WHITEHOLE the BLACKHOLE closure type, instead of INVALID_OBJECT
authorSimon Marlow <simonmar@microsoft.com>
Fri, 10 Mar 2006 20:42:56 +0000 (20:42 +0000)
committerSimon Marlow <simonmar@microsoft.com>
Fri, 10 Mar 2006 20:42:56 +0000 (20:42 +0000)
Just to keep sanity checking happy, and so we don't need a completely
new closure type.

ghc/rts/StgMiscClosures.cmm

index c29a474..70d08ae 100644 (file)
@@ -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!"); }
 
 /* ----------------------------------------------------------------------------