From: Alejandro Colomar <une+c@alejandro-colomar.es>
To: Philipp Klaus Krause <philipp@informatik.uni-frankfurt.de>
Cc: "sc22wg14@open-std. org" <sc22wg14@open-std.org>,
Robert Seacord <rcseacord@gmail.com>,
libc-alpha@sourceware.org, musl@lists.openwall.com,
linux-man@vger.kernel.org
Subject: Re: [SC22WG14.34662] n3752, alx-0029r8 - Restore the traditional realloc(3) specification
Date: Wed, 7 Jan 2026 21:00:37 +0100 [thread overview]
Message-ID: <aV66cpx76ciahOBN@devuan> (raw)
In-Reply-To: <4dda2463-3adf-4fdf-a2c9-d58a2cdce415@informatik.uni-frankfurt.de>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
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>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-01-07 20:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251223161139.196AB356CF9@www.open-std.org>
[not found] ` <20251223164349.F0BC5356D1A@www.open-std.org>
[not found] ` <CACqWKsOkbArXm0XBUHkLcFFwDUP8iDQv_xPeNbomR0bKf-GCFw@mail.gmail.com>
[not found] ` <20251223211529.6365A356CF9@www.open-std.org>
[not found] ` <CACqWKsNQCchFZnFKKAyi-3HDtJYQ6sc=UZeb+hX48WQ1e7yj_w@mail.gmail.com>
[not found] ` <20260106210527.AA3FA356D3A@www.open-std.org>
[not found] ` <20260106214930.A5C8E356D2B@www.open-std.org>
2026-01-06 23:08 ` n3752, alx-0029r8 - Restore the traditional realloc(3) specification Alejandro Colomar
[not found] ` <PH1P110MB1636A1DEC402A702C28EBA9ECC84A@PH1P110MB1636.NAMP110.PROD.OUTLOOK.COM>
2026-01-07 7:51 ` [SC22WG14.34664] " Alejandro Colomar
[not found] ` <PH1P110MB1636D74EDD4F3074AC98F12FCC84A@PH1P110MB1636.NAMP110.PROD.OUTLOOK.COM>
[not found] ` <PH1P110MB163601133BF0167C46C8CC9DCC84A@PH1P110MB1636.NAMP110.PROD.OUTLOOK.COM>
2026-01-07 17:30 ` Florian Weimer
2026-01-07 20:28 ` Alejandro Colomar
2026-01-08 11:18 ` Florian Weimer
2026-01-08 11:53 ` [musl] " Adhemerval Zanella Netto
2026-01-07 20:36 ` [SC22WG14.34672] " Alejandro Colomar
[not found] ` <20260108023757.3C908356D01@www.open-std.org>
2026-01-08 11:08 ` [SC22WG14.34681] " Alejandro Colomar
2026-01-07 20:16 ` [SC22WG14.34664] " Alejandro Colomar
2026-01-07 22:01 ` Joseph Myers
[not found] ` <20260107220138.AE8DF356CFB@www.open-std.org>
2026-01-08 14:59 ` [SC22WG14.34679] " Martin Uecker
[not found] ` <PH1P110MB16361EF635C579E30308D647CC85A@PH1P110MB1636.NAMP110.PROD.OUTLOOK.COM>
2026-01-08 16:26 ` Joseph Myers
[not found] ` <20260106221652.F02B3356D1A@www.open-std.org>
2026-01-06 23:15 ` [SC22WG14.34665] " Alejandro Colomar
[not found] ` <20260106201250.2A0A5356CEC@www.open-std.org>
[not found] ` <4dda2463-3adf-4fdf-a2c9-d58a2cdce415@informatik.uni-frankfurt.de>
2026-01-07 20:00 ` Alejandro Colomar [this message]
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=aV66cpx76ciahOBN@devuan \
--to=une+c@alejandro-colomar.es \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=musl@lists.openwall.com \
--cc=philipp@informatik.uni-frankfurt.de \
--cc=rcseacord@gmail.com \
--cc=sc22wg14@open-std.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.