[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2895768.DJkKcVGEfx@tjmaciei-mobl5>
Date: Tue, 11 Nov 2025 13:59:19 -0800
From: Thiago Macieira <thiago@...ieira.org>
To: James Y Knight <jyknight@...gle.com>, Rich Felker <dalias@...c.org>
Cc: Alejandro Colomar <alx@...nel.org>, musl@...ts.openwall.com,
The 8472 <the8472.rs@...inite-source.de>, Florian Weimer <fw@...eb.enyo.de>,
libc-alpha@...rceware.org, Arthur O'Dwyer <arthur.j.odwyer@...il.com>,
Jonathan Wakely <jwakely@...hat.com>
Subject: Re: Re: realloci(): A realloc() variant that works in-place
On Tuesday, 11 November 2025 12:51:28 Pacific Standard Time Rich Felker wrote:
> What is the actual problem folks are trying to solve?
>
> Has that ever been stated clearly?
Yes, more than once: growing a container (array, usually) that holds objects
with non-trivial copy/move operations. realloc() is unsuitable for that
because the elements can't be memmove()d, so containers today must allocate a
new buffer, perform the expensive move, then free the old buffer.
> Is it a single problem or multiple ones that keep getting raised
> because they seem vaguely related to the topic?
There are a few incidental requests, like finding out how big a buffer realy is,
when the allocation happens.
> Multiple people who are not participants in this thread but who have
> seen it have told me it looks like something out of the Simple
> Sabotage Field Manual and are frustrated to see myself and others
> having our time wasted on it.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Principal Engineer - Intel Data Center - Platform & Sys. Eng.
Download attachment "signature.asc" of type "application/pgp-signature" (871 bytes)
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.
