[GHC] #12357: Increasing maximum constraint tuple size significantly blows up compiler allocations

[GHC]

#12357: Increasing maximum constraint tuple size significantly blows up compiler
allocations
-------------------------------------+-------------------------------------
        Reporter:  bgamari           |                Owner:
            Type:  bug               |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  Compiler          |              Version:  7.10.3
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
 Type of failure:  Compile-time      |  Unknown/Multiple
  performance bug                    |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by bgamari):

 [[http://home.smart-cactus.org/~ben/ghc/tickets/T12357/Shapes-
 ticky.diff.html|Here's]] a diff of ticky output from `fulsom`'s `Shapes`
 module compiled with dd3080fe0263082f65bf2570f49189c277b12e28 and its
 parent. There's nothing particularly alarming here, as far as I can tell:
 most of the quantitative differences are in `IfaceType`, `Unique`,
 `Binary`, and `BinIface`, which all makes good sense given we now need to
 load more declarations from the `GHC.Classes` interface file.

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