Joerg Wunsch wrote: > In that case, looking at the compiler-generated assembly code (as > Julius suggested) is the best way. The compiler leaves a comment in > the assembly code indicating the depth of the stack frame.
This would only work on a subset of the algorithms I would like to measure, as it is difficult to automatize this kind of analysis if data depended allocations occur or recursive function calls are made (both happens in my bigint implementation). Isn't there a simple variable which indicates the top of the heap? Best regards, Daniel
signature.asc
Description: OpenPGP digital signature
_______________________________________________ AVR-chat mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-chat
