[GHC] #13360: Add a flag to enable inferring HasCallStack constraints

GHC ghc-devs at haskell.org
Wed Nov 1 10:28:17 UTC 2017


#13360: Add a flag to enable inferring HasCallStack constraints
-------------------------------------+-------------------------------------
        Reporter:  gridaphobe        |                Owner:  (none)
            Type:  feature request   |               Status:  new
        Priority:  normal            |            Milestone:  8.4.1
       Component:  Compiler          |              Version:  8.0.1
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by saurabhnanda):

 > Well, the overhead may (nearly) disappear entirely if the function with
 the constraint is inlined. If not then you will pay the cost of an
 additional pointer argument and possibly a constructor allocation.

 What would be a sensible way to benchmark this runtime cost? I'm in the
 process of evaluating the impact of enabling `HasCallstack` all throughout
 my code and am putting together a benchmark. The perf impact of
 `HasCallstack` would be significantly lower than compiling with profiling
 enabled, right?

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


More information about the ghc-tickets mailing list