On 12/01/2012 13:49, Wayne Uroda wrote: > Hello, > > I am interested in starting an open source tool for msp430 > development, specifically to perform static, whole elf analysis to > investigate stack usage. Such a tool can identify maximum stack depth > of each function and also find the maximum stack usage of an entire > executable. > > I have a tool which I wrote and use personally but it is limited and > specifically coded for the custom link setup I use for my company's > products, so I wish to start from scratch. > > Before I begin I just wanted to check that I wasn't reinventing the > wheel. How I have done it in the past was by parsing the output of > the disassembler, building a graph of function calls and then > analysing each function for instructions which modify the stack. > Would I be better off trying to insert this functionality into the > compiler/linker/disassembler itself? I have a feeling this would be a > lot more complicated. > > I plan on using C++. Any comments are welcome. > > Thanks, - Wayne Uroda >
I don't know if it will be of much use to you, but it is possible you can look at how doxygen generates call graphs and see if you can re-use code or ideas. mvh., David ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
