Sender:	rich AT phekda DOT freeserve DOT co DOT uk
Message-ID:	<3EECBA0F.9D6D4B30@phekda.freeserve.co.uk>
Date:	Sun, 15 Jun 2003 19:25:19 +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 <djgpp-workers AT delorie DOT com>
Subject:	nmalloc integration issues: memalign, names
Reply-To:	djgpp-workers AT delorie DOT com

Hello.

I've just started looking at integrating nmalloc. CBFalconer: I have a couple
of problems:

* memalign relies on <libc/malloc.h>. As I understand it, nmalloc uses a
different memory-block format than the current implementation.

memalign is new in 2.04. CBFalconer, please please please check out CVS! This
needs fixing, before I can integrate the code. You will need a CVS checkout
anyway for later maintenance.

What should we do with the new block format? Put it in <libc/malloc.h>? Or
should <libc/malloc.h> become an empty header? (It seems to me like the block
format should go in <libc/malloc.h>.)

* I don't like the names of the hook things in sysquery.h. malloc_HK, etc. I
think should be prefixed with two underscores, since this stuff is
library-internal. I think m_* and M_* should be expanded to __malloc_* and
__MALLOC_*.

* Please tell me how you see the files mapping into CVS. I have my ideas, but
I'd like to know what you think.

My current plan is not to remove any files, just add the new ones and change
the Makefile. This plan does not work so well with texinfo files. Perhaps I
could rename .txh -> .txo, so that they're still present in CVS. I guess this
doesn't add anything, so maybe it's better if I just add nmalloc.txh and
remove the old files.

I will apply a tag before I do any updates: PRE_NMALLOC_IMPORT, probably.

Bye, Rich =]

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

- Raw text -