Thanks for the responses. I guess that confirms that my problem is down to the memory allocation.
Pedro Alves wrote: > You could try reusing it, and/or writing your own > global operator new, operator delete, etc. This sounds like a good idea - I think that I'll try that. I guess I can extract the relevant code from newlib. > However, if you find that you can isolate the parts of > the code that are critical, it may be better to use a pool > or a special allocator for the memory management of those > time critical allocations/objects. I did try this for some classes for the linux port of this code, but the gain was very small. I guess that dlmalloc is just well-suited to this code! Hywel. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
