unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Eric Wong <e@80x24.org>
Cc: libc-alpha@sourceware.org
Subject: Re: status of dj/malloc branch?
Date: Mon, 01 Apr 2024 16:59:18 -0400	[thread overview]
Message-ID: <xnh6gk6bq1.fsf@greed.delorie.com> (raw)
In-Reply-To: <20240401191925.M515362@dcvr> (message from Eric Wong on Mon, 1 Apr 2024 19:19:25 +0000)


If you're wondering about the branch itself, the harsh answer is that
I'm not maintaining it.

If you're wondering about the goals therein, IIRC we discovered we had
no good way to visualize and analyze the heap itself in order to
understand what causes the problem we're trying to solve.  While these
are solvable problems, they're big projects and never quite made it to
the top of our priority lists.



  reply	other threads:[~2024-04-01 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 19:19 status of dj/malloc branch? Eric Wong
2024-04-01 20:59 ` DJ Delorie [this message]
2024-04-06 22:02   ` Eric Wong
2024-04-08 18:37     ` DJ Delorie

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

  List information: https://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=xnh6gk6bq1.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=e@80x24.org \
    --cc=libc-alpha@sourceware.org \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).