mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] mallocng switchover - opportunity to test
Date: Wed, 10 Jun 2020 23:49:34 -0400	[thread overview]
Message-ID: <20200611034934.GL1079@brightrain.aerifal.cx> (raw)
In-Reply-To: <20200609035010.GE1079@brightrain.aerifal.cx>

On Mon, Jun 08, 2020 at 11:50:10PM -0400, Rich Felker wrote:
> I just pushed a series of changes in preparation for upstreaming
> mallocng. Before it's actually imported, it can be tested by
> performing the following simple 4 steps:
> 
> 1. mkdir src/malloc/mallocng
> 2. echo "MALLOC_DIR = mallocng" >> config.mak
> 3. Dropping the attached files into src/malloc/mallocng
> 4. Symlinking or copying meta.h, malloc.c, realloc.c, free.c,
>    malloc_usable_size.c, and aligned_alloc.c from mallocng source dir
>    to src/malloc/mallocng. (You can also include dump.c if desired.)
> 
> This produces a near-fully-integrated malloc, including support for
> reclaim_gaps donation from ldso. The only functionality missing, which
> I expect to flesh out before actual import, is handling of the case of
> incomplete malloc replacement by interposition (__malloc_replaced!=0).
> 
> Please report any problems encountered.

For reference -- I should have mentioned in the original post -- the
above is with musl commit 384c0131ccda2656dec23a0416ad3f14101151a7
and mallocng-draft commit c0d6d87596f565e652e126f54aa1a2afaecc0e52.

I'll have an update to these posted soon.

Rich

  parent reply	other threads:[~2020-06-11  3:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09  3:50 Rich Felker
2020-06-09 11:09 ` Szabolcs Nagy
2020-06-09 20:08   ` Rich Felker
2020-06-10  0:58     ` Rich Felker
2020-06-10  8:33       ` Szabolcs Nagy
2020-06-11 20:05         ` Rich Felker
2020-06-12 17:42           ` Szabolcs Nagy
2020-06-10  9:19     ` Szabolcs Nagy
2020-06-10 16:41       ` Rich Felker
2020-06-11  3:49 ` Rich Felker [this message]
2020-06-11  4:33   ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200611034934.GL1079@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).