Message-ID:	<3EF00098.5FE616DE@yahoo.com>
Date:	Wed, 18 Jun 2003 02:03:04 -0400
From:	CBFalconer <cbfalconer AT yahoo DOT com>
Organization:	Ched Research
X-Mailer:	Mozilla 4.75 [en] (Win98; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: nmalloc integration issues: memalign, names
References:	<3EECBA0F DOT 9D6D4B30 AT phekda DOT freeserve DOT co DOT uk> <3EECD63E DOT 19C52226 AT yahoo DOT com> <3EEE24E7 DOT E7B03AB0 AT phekda DOT freeserve DOT co DOT uk> <3EEE3821 DOT 2C04E9D4 AT yahoo DOT com> <3EEF6925 DOT 43CCBDBB AT phekda DOT freeserve DOT co DOT uk> <3EEFD834 DOT 45AD84AE AT yahoo DOT com> <2950-Wed18Jun2003064448+0300-eliz AT elta DOT co DOT il>
Reply-To:	djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> > From: CBFalconer <cbfalconer AT yahoo DOT com>
> >
> > <rant>
> > Now take a look at the frustrations from my viewpoint.
> 
> Yes, it does take an effort to add something substantial to the DJGPP
> library.  We appreciate that effort, believe me.
> 
> We now ask you for an additional effort, one that, for you, is much
> smaller than the one that went into programming and debugging nmalloc:
> that you make it compatible with related library interfaces.  It is
> unrealistic to expect from another volunteer to work on code they are
> not yet familiar with just because you don't have a sufficiently new
> version of the library code and cannot look at that yourself.  It is
> also unreasonable to expect us to replace malloc with something that
> breaks some of related features.  Each feature we put into DJGPP is
> sorely needed somewhere (Mark explained in this thread why memalign
> and friends were added: to be able to port latest versions of GCC), so
> we cannot afford to stop their support.  We need nmalloc to be
> compatible with memalign.
... snip ...
> 
>   http://www.ludd.luth.se/~ams/djgpp/cvs/
> 
> All you need is point your favorite Web browser at that URL and
> download the file djgpp.cvs.tar.gz from there.  It's only 2.2MB, which
> should be small enough even for the most slow connection these days.
> 
> Please make this additional small effort to allow Richard to put
> nmalloc into the next alpha release.

I can go get that, but what the d*evil am I looking for?  Mark E.
brought up another herd of interfaces?  Where does it end?  I
don't want to rebuild everything.  I have no idea how long it will
take to implement.  Basically I am thinking that nmalloc assigns
an overlarge piece, saws off the head and puts it in the free
list, saws off the tail and put that in the free list, and returns
the remainder.  This will definitely complicate nmalloc.  And I
have doubts that it is the right approach.  

And what about those other things, vmalloc, mmap, whatever?

-- 
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net)
   Available for consulting/temporary embedded and systems.
   <http://cbfalconer.home.att.net>  USE worldnet address!

- Raw text -