Changes between Version 2 and Version 3 of Commentary/Rts/HaskellExecution/FunctionCalls
- Timestamp:
- 02/17/11 09:49:07 (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Commentary/Rts/HaskellExecution/FunctionCalls
v2 v3 28 28 When compiling a call, there are several cases to consider, which are treated separately. 29 29 30 * '''Unknown function'''; a call in which we do not statically know what the function is. In that case we must do a "generic apply". This is so exciting that it deserves its [wiki:Commentary/Rts/HaskellExecution #Genericapply own section].30 * '''Unknown function'''; a call in which we do not statically know what the function is. In that case we must do a "generic apply". This is so exciting that it deserves its [wiki:Commentary/Rts/HaskellExecution/FunctionCalls#Genericapply own section]. 31 31 32 32 * '''Known function, saturated call'''. The function is applied to exactly the right number of arguments to satisfy its arity. In that case, we simply load the arguments according to the standard entry convention, and tail-call (jump to) the function's entry point. On average, about 80% of all calls fall into this category (see the eval/apply paper for measurements).
