Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGg_6+OWhJ3si5sUpa1UY6ZxRtEcyTTvbG44E6Zi=w8ehee=YQ@mail.gmail.com>
Date: Wed, 7 Jan 2026 20:37:15 -0600
From: Nevin Liber <nevin@...usplusguy.com>
To: David Svoboda <svoboda@...t.org>
Cc: Alejandro Colomar <une+c@...jandro-colomar.es>, Robert Seacord <rcseacord@...il.com>, 
	"sc22wg14@...n-std. org" <sc22wg14@...n-std.org>, Florian Weimer <fweimer@...hat.com>, 
	"Carlos O'Donell" <carlos@...hat.com>, Aaron Ballman <aaron@...onballman.com>, 
	"libc-alpha@...rceware.org" <libc-alpha@...rceware.org>, 
	"musl@...ts.openwall.com" <musl@...ts.openwall.com>, 
	"linux-man@...r.kernel.org" <linux-man@...r.kernel.org>
Subject: Re: [SC22WG14.34672] n3752, alx-0029r8 - Restore the traditional
 realloc(3) specification

On Wed, Jan 7, 2026 at 8:31 AM David Svoboda <svoboda@...t.org> wrote:

> Here are some more thoughts on n3752
> [...]
> WRT this text:
>
>         Code written for platforms returning a null pointer can be
> migrated to platforms returning non-null, without significant
> issues.
>
> I am very skeptical that this is indeed true. But to be precise, this is
> Glibc's problem rather than WG14's.  If they are willing to change glibc to
> return non-null on realloc(0), then I am willing to agree to this change in
> ISO C.
>
> Is there any evidence that changing this behavior breaks no code?  Any
> test failures?  Any surveys?
>

And if it breaks no code, is that because this is a corner case that
doesn't occur in practice?  That in itself doesn't mean we shouldn't change
it.


> This paper ignores Windows other than to mention that it would need to
> change too.  I doubt MS will update MSVC to accommodate this paper.   So
> accepting this paper makes MSVC noncompliant.
>

This is the part that is troublesome to me.  What is the point of changing
this behavior if two (or even just one) major implementations are going to
ignore it?
-- 
 Nevin ":-)" Liber  <mailto:nevin@...usplusguy.com <nevin@...loverlord.com>>
+1-847-691-1404

Content of type "text/html" skipped

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.