Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <aV66cpx76ciahOBN@devuan>
Date: Wed, 7 Jan 2026 21:00:37 +0100
From: Alejandro Colomar <une+c@...jandro-colomar.es>
To: Philipp Klaus Krause <philipp@...ormatik.uni-frankfurt.de>
Cc: "sc22wg14@...n-std. org" <sc22wg14@...n-std.org>, 
	Robert Seacord <rcseacord@...il.com>, libc-alpha@...rceware.org, musl@...ts.openwall.com, 
	linux-man@...r.kernel.org
Subject: Re: [SC22WG14.34662] n3752, alx-0029r8 - Restore the traditional
 realloc(3) specification

Hi Philipp,

On Wed, Jan 07, 2026 at 02:55:03PM +0100, Philipp Klaus Krause wrote:
> Am 06.01.26 um 21:12 schrieb Robert Seacord:
> > I'm still waiting to hear from GCC that they plan to change the behavior
> > of realloc and break their existing code.  If GCC plans to do this, it
> > could well change my vote.
> 
> Not GCC here.
> 
> SDCC changed its malloc/realloc aligning it with Alejandro's proposal a few
> months ago, and the new behaviour will be in the next release (SDCC 4.6.0).
> 
> We made this decision after discussion among SDCC developers and users, and
> think that this is the best solution for SDCC and its users. We are not
> making any statement about this solution being appropriate for the standard
> or other implementations.

Wow!  Thanks!  That makes it two implementations that have already
changed to adapt to this behavior after the proposal:

	-  SDCC (SDCC 4.6.0)
	-  gnulib (2024-11)

Plus of course the POSIX standard itself.  That's looking good.


Have a lovely night!
Alex

> 
> Philipp
> 

-- 
<https://www.alejandro-colomar.es>

Download attachment "signature.asc" of type "application/pgp-signature" (834 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.