>
LispWorks IDE User Guide>
24 The Profiler>
24.7 Profiling pitfalls 24.7.5 Effect of compiler optimizationsWith certain compiler settings code can be optimized such that the Profiler data does not appear to match your source code. For example when a tail call is optimized, the tail-called function appears in the call tree as a child of the parent of the caller, rather than as a child of its caller (just as in the debugger stack). Similarly code using funcall
or apply
may yield confusing results. To prevent tail-call optimization, use compiler setting debug 3
.
LispWorks IDE User Guide (Windows version) - 25 Nov 2011
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4