[GHC] #15155: How untagged pointers sneak into banged fields

[GHC]

#15155: How untagged pointers sneak into banged fields
-------------------------------------+-------------------------------------
        Reporter:  heisenbug         |                Owner:  heisenbug
            Type:  bug               |               Status:  new
        Priority:  normal            |            Milestone:  8.8.1
       Component:  Compiler          |              Version:  8.4.2
      Resolution:                    |             Keywords:  CodeGen
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:  14677
 Related Tickets:  #13027 #7308      |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by simonpj):

 But see comment:11.  I now think that it's a lost cause to insist that a
 strict constructor field is always a correctly-tagged pointer to an
 evaluated data value.  In which case the whole IND_STATIC change becomes
 moot.

 I think we should work on the other tickets identified in commment:1. Are
 you interested in pursuing any of them?

-- 
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/15155#comment:15>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler