From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Florian Weimer <fweimer@redhat.com>,
Zack Weinberg via Libc-alpha <libc-alpha@sourceware.org>
Cc: Zack Weinberg <zack@owlfolio.org>
Subject: Re: [RFC] Supporting malloc_usable_size
Date: Tue, 6 Dec 2022 14:25:53 -0500 [thread overview]
Message-ID: <dec0d13b-72f3-e850-3921-e28fa11c760f@gotplt.org> (raw)
In-Reply-To: <87359tpp1m.fsf@oldenburg.str.redhat.com>
On 2022-12-05 15:35, Florian Weimer via Libc-alpha wrote:
> I think it's a backwards-incompatible change. The existing manual page
> documents the function as MT-Safe.
>
> With this new policy, I don't think malloc_usable_size is useful for
> anything at all, and we can just deprecate it (with a deprecation
> warning message) and eventually remove it from linking (after
> considering the impact on replacement malloc implementations, but I
> don't think it will be problematic).
We don't have consensus on deprecation unfortunately. DJ is of the
opinion that the limited use (knowing the usable size but not being able
to do anything with it) may be useful enough for some programs. With
that position, making it clear that the extra space is never safely
usable and then just leaving it at that is probably the least worst out.
Sid
next prev parent reply other threads:[~2022-12-06 19:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 21:32 Siddhesh Poyarekar
2022-12-02 4:42 ` DJ Delorie
2022-12-02 5:00 ` Sam James
2022-12-02 5:28 ` DJ Delorie
2022-12-02 12:36 ` Siddhesh Poyarekar
2022-12-02 19:16 ` DJ Delorie
2022-12-02 19:49 ` Siddhesh Poyarekar
2022-12-02 19:57 ` DJ Delorie
2022-12-02 12:03 ` Andreas Schwab
2022-12-02 12:22 ` Siddhesh Poyarekar
2022-12-02 12:34 ` Andreas Schwab
2022-12-02 12:39 ` Florian Weimer
2022-12-05 18:46 ` Zack Weinberg
2022-12-05 19:04 ` Siddhesh Poyarekar
2022-12-05 20:35 ` Florian Weimer
2022-12-06 19:25 ` Siddhesh Poyarekar [this message]
2022-12-07 10:01 ` Florian Weimer
2022-12-07 16:34 ` Siddhesh Poyarekar
2022-12-07 16:54 ` Adhemerval Zanella Netto
2022-12-07 16:57 ` Sam James
2022-12-07 17:39 ` Florian Weimer
2022-12-09 15:42 ` Siddhesh Poyarekar
2022-12-07 18:45 ` DJ Delorie
2022-12-02 12:54 ` Florian Weimer
2022-12-02 13:54 Wilco Dijkstra
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=dec0d13b-72f3-e850-3921-e28fa11c760f@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=zack@owlfolio.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).