#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): Phab:D2400 Wiki Page: | -------------------------------------+------------------------------------- Comment (by bgamari): And as it turns out wiring in the tuple type constructors representations has further knock-on consequence, requiring that we yet again wire-in `Data.Typeable.Internal.Module` and `Data.Typeable.Internal.TrName`. Recall that we unwired these around six months ago (ticket:11120#comment:28) due to breakage in GHCJS due to the varying width of `Fingerprint` on 32- and 64-bit platforms. For what it's worth, this varying width would be fixed if #11953 were implemented. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12357#comment:32 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler