I don't mean to be glib by saying this, but in principle it's simple: find out why you have a problem, and then fix it. Where is the memory going? is it the code memory or data memory? if code, identify the large routines, and find out if runtime libraries are being linked in. The old chestnut used to be that people would leave in some leftover debugging printf() statements in if(0) sections, which would pull in floating point formatting I/O library code. If you have too much data memory, see if you can pack or even overlay your data structures. In any case you need to measure first; once you do that, there are people on this list that do this kind of thing every day and should be able to give you more specific advice.
On Feb 13, 2008 1:25 PM, Mark Rages <[email protected]> wrote: > Hi, > > I am running tight on RAM with my MSP project. What are the best > practices for optimizing memory usage? How do you measure it? I > would be grateful for any tricks you can share. > > Regards, > Mark > markra...@gmail > -- > Mark Rages, Engineer > Midwest Telecine LLC > [email protected] > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users >
