[GHC] #9798: Frustrating behaviour of the INLINE pragma

[GHC]

#9798: Frustrating behaviour of the INLINE pragma
-------------------------------------+-------------------------------------
              Reporter:  mojojojo    |            Owner:
                  Type:  bug         |           Status:  new
              Priority:  normal      |        Milestone:
             Component:  Compiler    |          Version:  7.8.3
            Resolution:              |         Keywords:
      Operating System:  MacOS X     |     Architecture:  x86_64 (amd64)
       Type of failure:  Runtime     |       Difficulty:  Unknown
  performance bug                    |       Blocked By:
             Test Case:              |  Related Tickets:
              Blocking:              |
Differential Revisions:              |
-------------------------------------+-------------------------------------

Comment (by simonpj):

 I can see that is frustrating.

 There are a lot of dependencies here.  (Though, happily, I believe that
 one can run your benchmark without having any C stuff installed eg
 postgres.  Is that right?)

 But still, there's a lot of stuff.  Could you
  * compile just the offending module (which is `Decoder.hs` I think),
  * on its own,
  * preferably with only the definition for `numeric` (which is the
 offending one I think)
  * with the extra flags `-dverbose-core2core -ddump-inlinings`
 and save the three results for Step 1/2/3 attached to this ticket?  That
 would mean I could take a look without reproducing the setup.

 Another thing that would be revealing would be to add `-ticky` to the
 command line when compiling; and `+RTS -rstep1.ticky` to the command line
 when running.  And then add the `.ticky` files to the ticket.  That should
 show up where the performance differences are occurring without affecting
 anything.

 Thanks

 Simon

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