On 6 July 2011 16:40, Simon Marlow <[email protected]> wrote: > When the data type has more constructors than we have room for in the tag > bits, then the code for the alternatives will grab the tag from the info > table. If the info table is IND_STATIC_info, this will go wrong.
I see. I have read the code and it looks like the srt_bitmap field in the info table is only inspected for THUNK and FUN closures. So in theory I could make this work by generating a fresh IND_STATIC info table for each use site with the appropriate tag filled out. I'm not sure if this is very satisfactory, even though it would probably work. We could mark each generated IND_STATIC info table as non-exported, so it *would* exported reduce symbol count. Max _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
