From: Alejandro Colomar <une+c@alejandro-colomar.es>
To: Robert Seacord <rcseacord@gmail.com>,
C Committee <sc22wg14@open-std.org>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
musl@lists.openwall.com, Florian Weimer <fweimer@redhat.com>,
David Svoboda <svoboda@cert.org>,
Robert Seacord <rcseacord@gmail.com>,
"sc22wg14@open-std. org" <sc22wg14@open-std.org>,
Carlos O'Donell <carlos@redhat.com>,
Aaron Ballman <aaron@aaronballman.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
Paul Eggert <eggert@cs.ucla.edu>
Subject: Updates on n3752, alx-0029r8 - Restore the traditional realloc(3) specification
Date: Tue, 20 Jan 2026 23:07:12 +0100 [thread overview]
Message-ID: <aW_51O7XVxxAMXby@devuan> (raw)
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
Hi Robert, and all,
I've been talking with the team at Microsoft that is responsible for
realloc(3).
They are "definitely interested in incorporating the change". They are
also going to "coordinate [with the OS group] to perform thorough
testing to understand the impact of the change".
This may take some time, and will come back to me with the feedback of
that. The communication with them is quite fluent, BTW.
I think this is great news for fixing and unifying realloc(3). Also,
it's also great to see a big company like Microsoft will put their
resources into testing this, as they have resources that we voluntary
maintainers of open source projects don't have (or would have to take
from some other changes).
Robert, I'd like to withdraw the paper from the next meeting. I'll
write a new paper once Microsoft tells me their testing results and
feedback, incorporating them.
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2026-01-20 22:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aW_51O7XVxxAMXby@devuan \
--to=une+c@alejandro-colomar.es \
--cc=aaron@aaronballman.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=musl@lists.openwall.com \
--cc=rcseacord@gmail.com \
--cc=sc22wg14@open-std.org \
--cc=svoboda@cert.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