Joined: Mon Dec 12, 2016 5:07 pm Posts: 18
|
Andes provides an alternative tool "stack-size.pl" to roughly estimate the stack size of an adx file. Put the file at the adx folder. Then, issue the following command with a toolchain cygwin. A log file is generated.
$ ./stack-size.pl --summary xxxx.adx > stack-size.log ------------------------------------------ There are three parts in the log file 1. Call graph: Function Self Parent Line File User/Lib vprintf_help 16 0 lib nds_write 16 16 lib uart_put_char 0 32 lib uart_put_char -1 -1 lib __cmpdf2 0 0 lib __nedf2 0 0 lib reset_handler 4 0 lib
2. Max stack size used by top-level functions (sorted):
Function Stack double2dec 1288 UART2_ISR 700 CRYPTO_ISR 44 reset_handler 40 vprintf_help 32 __ltdf2 0 __gtdf2 0
3. Max stack path (1288 bytes):
Function Stack double2dec 1240 sep_frac 48
|
|