Mail Archives: djgpp/2008/07/08/01:22:48
DJ Delorie wrote:
>> Well, I prepared the malloc replacement (nmalloc), together with the
>> debug routines, several years ago, and it has never been
>> incorporated. This seriously harms enthusiasm.
>
> Did you ever resolve all the issues we had with it?
>
I got random crashes when I last stress-tested it. Tests included only allocation
of huge amount of small random size memory blocks (I don't remember size
exactly, but about some tenth of bytes, total size of all blocks were well above
100 MB). No similar behavior observed with malloc from DJGPP CVS.
It is however used in my last builds of GCC-4.3.[01]. Otherwise slowness of free()
would make them almost unusable. I have not noticed crashes of these GCC versions
however.
Andris
PS. GCC-4.3.1 is not released for DJGPP yet, because of problems with DJGPP v2.03.
We perhaps need extra rerelease of DJGPP v2.03 or release GCC-4.3.1 for v2.04pre
only.
- Raw text -