X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Message-ID: <4872F99B.20003@iki.fi> Date: Tue, 08 Jul 2008 08:22:35 +0300 From: Andris Pavenis User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 CC: djgpp AT delorie DOT com Subject: Re: libstdc++ writev/2.04/patches upstream? References: <200807070405 DOT m67451dZ010910 AT delorie DOT com> <200807071920 DOT m67JKA4v032518 AT envy DOT delorie DOT com> <487290E2 DOT 86197C00 AT yahoo DOT com> <200807072300 DOT m67N0t0Y005696 AT envy DOT delorie DOT com> In-Reply-To: <200807072300.m67N0t0Y005696@envy.delorie.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com 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.