[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140310105512.GO7372@port70.net>
Date: Mon, 10 Mar 2014 11:55:14 +0100
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: Re: Release schedule & tasks for 1.0
* juris <juris@...lv> [2014-03-10 09:50:54 +0000]:
>
> Not exactly a bug fix, but does something like this qualify for 1.0 inclusion?
> Lifted it from http://article.gmane.org/gmane.linux.lib.musl.general/1255/ and prettied up a little.
>
symbols like this must be added in a non-polluting way
(ie. it is not ok to pull such a symbol into every
statically linked binary that uses malloc, nor to
make it visible in a c standard header by default)
and there should be a good reason to add it
(ie. existing code using it or standard defining it)
> +
> +size_t malloc_usable_size(void *p)
> +{
> + return CHUNK_SIZE(MEM_TO_CHUNK(p)) - OVERHEAD;
> +}
if (!p) return 0; is missing
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
