"Daniel Otte" <[email protected]> wrote: > I intend to measure only the memory footprint of some function and > in this special case there is no heap memory used by the functions.
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. Note that things like the .lst files do *not* display the *generated* assembly code, they display the disassembly code. Better directly create the assembly code (use -S instead of -c), and have a look there. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ AVR-chat mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-chat
