This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: extend dl-minimal malloc implementation
- From: Florian Weimer <fweimer at redhat dot com>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: DJ Delorie <dj at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 11 Aug 2017 14:44:51 +0200
- Subject: Re: extend dl-minimal malloc implementation
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=fweimer at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com D0F11A1F46
- References: <xnk23vy3ln.fsf@greed.delorie.com> <0a5122c8-a6f8-0351-0682-9a5ede15891d@redhat.com> <CAEMqeSpRmyH=pUzbjmW6pPeWqV9SorXsDdNXdZt8pkFpO5a12A@mail.gmail.com>
On 08/11/2017 02:09 PM, Carlos O'Donell wrote:
> I think we should push this upstream. It allows the full malloc API to be
> used effectively instead of alloca.
>
> Are we worried about something?
I'm not sure we have consensus to move from alloca to malloc. The IFUNC
scheduler needs some allocator, but I'm no longer certain the minimal
malloc will work for it because we are switching the malloc
implementation as part of the relocation.
There is some code to ensure that the dynamic linker itself is relocated
last, but I don't know how effective it is in practice.
I'm also concerned that without block merging on free, we can't return
any allocated memory to the operating system once the initial relocation
is finished.
Florian