[GHC] #9315: Weird change in allocation numbers of T9203

[GHC]

#9315: Weird change in allocation numbers of T9203
-------------------------------------+-------------------------------------
              Reporter:  nomeata     |             Owner:  simonmar
                  Type:  bug         |            Status:  new
              Priority:  normal      |         Milestone:
             Component:  Runtime     |           Version:  7.9
  System                             |          Keywords:
            Resolution:              |  Operating System:  Unknown/Multiple
Differential Revisions:              |   Type of failure:  None/Unknown
          Architecture:              |         Test Case:
  Unknown/Multiple                   |          Blocking:
            Difficulty:  Unknown     |
            Blocked By:              |
       Related Tickets:              |
-------------------------------------+-------------------------------------

Comment (by simonmar):

 The perf tests don't guarantee to pass unless you use the validate
 settings, I think that's unavoidable.  Maybe it's possible to just skip
 them unless the correct settings are being used.

 We don't use -O2 in validate because validate is supposed to be fast.  But
 that doesn't render the perf tests useless, they're just testing -O and
 not -O2 (and individual tests can use -O2 if we want).

 Should we force -O2 for Data.Typeable.Internal?  A tricky one.  I
 generally don't like forcing optimisation settings for individual modules
 like this, because it prevents us from seeing the real effect of global
 optimisation settings.

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