From 4cb89d670945dfcb747d0ab74ac89dd9348ed6cd Mon Sep 17 00:00:00 2001 From: Simon Marlow Date: Fri, 10 Mar 2006 20:42:56 +0000 Subject: [PATCH] Give WHITEHOLE the BLACKHOLE closure type, instead of INVALID_OBJECT Just to keep sanity checking happy, and so we don't need a completely new closure type. --- ghc/rts/StgMiscClosures.cmm | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/ghc/rts/StgMiscClosures.cmm b/ghc/rts/StgMiscClosures.cmm index c29a474..70d08ae 100644 --- a/ghc/rts/StgMiscClosures.cmm +++ b/ghc/rts/StgMiscClosures.cmm @@ -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!"); } /* ---------------------------------------------------------------------------- -- 1.7.10.4