Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3EEF6925.43CCBDBB@phekda.freeserve.co.uk>
Date: Tue, 17 Jun 2003 20:16:53 +0100
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
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>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

CBFalconer wrote:
> 
> Richard Dawe wrote:
> > CBFalconer wrote:
> > > Richard Dawe wrote:
> > > >
> ... snip ...
> >
> > >From src/libc/compat/stdlib/memalign.txh:
[snip]
> > I don't think it would be hard to implement. I'd do it myself,
> > except that I can't contribute any code at the moment, because
> > I need a disclaimer from my new employer.
> 
[snip]
> I don't remember seeing any mention of it here.  I am very leery
> of saying I can do anything now, because I expect to be taking off
> for a couple of months shortly.  I can see my way to implementing
> it within nmalloc, though, if it doesn't need a special realloc.

It was committed to CVS on 20 Jan 2001, according to my archives of djgpp-cvs.

Now I'm getting slightly frustrated - I feel like I'm banging my head against
a wall. We've tried gently persuading you to look at CVS or a snapshot of CVS
from MartinS every time nmalloc has come up recently. Now you say you didn't
know about memalign. That's not really surprising, since you haven't looked at
CVS (or a snapshot thereof).

Given that nmalloc isn't a slot-in replacement for the current memory
allocation functionality, one of the two will happen before alpha 2:

(1) someone takes your patch and rewrites memalign to work with nmalloc; or
(2) nmalloc doesn't go in.

Given how little time anyone seems to have for DJGPP these days, I'm guessing
(2) will occur.

Please don't take this as a slap in the face. On Sunday afternoon I was ready
and poised (and more than happy) to commit nmalloc to CVS. But if it's not a
slot-in replacement, then I don't think it can go in to alpha 2.

> With my systems hat on I can see the utility of a memalign
> operation, but why for DJGPP? Those low level abilities (e.g.
> paging) are all handled within Windoze anyhow or are not needed
> under other OSs.  In fact, without tying to actual (non-virtual)
> addresses it seems pretty pointless to me.
[snip]

memalign is supported by glibc. So is the function valloc, which uses
memalign. I'm assuming that they were added to DJGPP for compatibility with
glibc. Or since Mark E added them, perhaps they were added to ease porting of
bash.

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]