Sender:	rich AT phekda DOT freeserve DOT co DOT uk
Message-ID:	<3EF0E950.2B1F3581@phekda.freeserve.co.uk>
Date:	Wed, 18 Jun 2003 23:36:00 +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:	<3EEF6725 DOT 29821 DOT 7BD30 AT localhost> <3EEFDD57 DOT 8838C657 AT yahoo DOT com>
Reply-To:	djgpp-workers AT delorie DOT com

Hello.

CBFalconer wrote:
> 
> "Mark E." wrote:
> >
> > > 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
> >
> > valloc and memalloc were added because at the time g++'s internal
> > garbage collector required either valloc or mmap. I also seem to
> > remember that around that time valloc or mmap became a requirement
> > for gnu smalltalk.
> 
> Here is *another* new item or three.  What are valloc and
> memalloc?  What is mmap?
[snip]

valloc allocates memory aligned to the page size. It's currently implemented
by calling memalign.

I don't know about memalloc.

mmap allows files or devices to be mapped into memory. You can also use mmap
to allocate memory. DJGPP does not support mmap.

So as far as I can tell, the only function that needs reimplementing for
nmalloc to go in is memalign. So hopefully it's not as bad as it seemed.

Bye, Rich =]

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

- Raw text -