[GHC] #8589: Bad choice of loop breaker with INLINABLE/INLINE

[GHC]

#8589: Bad choice of loop breaker with INLINABLE/INLINE
--------------------------------------------+------------------------------
        Reporter:  NickSmallbone            |            Owner:
            Type:  bug                      |           Status:  new
        Priority:  normal                   |        Milestone:
       Component:  Compiler                 |          Version:  7.6.3
      Resolution:                           |         Keywords:
Operating System:  Unknown/Multiple         |     Architecture:
 Type of failure:  Runtime performance bug  |  Unknown/Multiple
       Test Case:                           |       Difficulty:  Unknown
        Blocking:                           |       Blocked By:
                                            |  Related Tickets:
--------------------------------------------+------------------------------

Comment (by simonpj):

 Currently the only (useful) behaviour of INLINEABLE for recursive
 functions is to allow type-class-overloaded functions to be specialised.
 That's why I think a name-change might be in order.

 We never specialise non-overloaded functions; doing so would simply
 generate two copies of the same machine code.

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