Changes between Version 4 and Version 5 of Commentary/Rts/HaskellExecution/FunctionCalls


Ignore:
Timestamp:
Sep 9, 2017 11:48:34 AM (2 years ago)
Author:
takenobu
Comment:

Modify link for community.haskell.org

Legend:

Unmodified
Added
Removed
Modified
  • Commentary/Rts/HaskellExecution/FunctionCalls

    v4 v5  
    55Source files: [[GhcFile(rts/Apply.h)]], [[GhcFile(rts/Apply.cmm)]]
    66
    7 Dealing with calls is by far the most complicated bit of the execution model, and hence of the code generator.  GHC uses an ''eval/apply'' strategy for compiling function calls; all the details of the design are in the paper [http://community.haskell.org/~simonmar/papers/evalapplyjfp06.pdf Making a fast curry: push/enter vs. eval/apply for higher-order languages].
     7Dealing with calls is by far the most complicated bit of the execution model, and hence of the code generator.  GHC uses an ''eval/apply'' strategy for compiling function calls; all the details of the design are in the paper [http://simonmar.github.io/bib/papers/evalapplyjfp06.pdf Making a fast curry: push/enter vs. eval/apply for higher-order languages].
    88
    99First, we need some terminology: