From: Paul Eggert <eggert@cs.ucla.edu>
To: libc-alpha@sourceware.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: [PATCH v3 0/4] malloc doc fixes for alignment
Date: Thu, 12 Feb 2026 10:18:10 -0800 [thread overview]
Message-ID: <20260212182031.107003-1-eggert@cs.ucla.edu> (raw)
This patch series affects only the manual. Tt adds documentation for
max_align_t and documents how malloc and friends align their results.
Also, it says that systems where malloc (0) returns NULL are now rare,
and reorganizes for clarity to separate examples from portability notes.
v3 incorporates comments from DJ Delorie in:
https://sourceware.org/pipermail/libc-alpha/2026-February/175060.html
https://sourceware.org/pipermail/libc-alpha/2026-February/175061.html
https://sourceware.org/pipermail/libc-alpha/2026-February/175062.html
v2 incorporated comments from Floriam Weimer and Wilco Dijkstra in:
https://sourceware.org/pipermail/libc-alpha/2026-February/174910.html
https://sourceware.org/pipermail/libc-alpha/2026-February/174994.html
https://sourceware.org/pipermail/libc-alpha/2026-February/174911.html
https://sourceware.org/pipermail/libc-alpha/2026-February/174916.html
As a result there is now a new, 4th patch that adds documentation on
possible future changes.
Paul Eggert (4):
Document max_align_t
Document malloc alignment
Say malloc (0) != NULL is now common; resection
malloc: alignment might change in future versions
NEWS | 7 ++-
manual/lang.texi | 28 +++++++---
manual/memory.texi | 131 ++++++++++++++++++++++++++++++++++++---------
3 files changed, 131 insertions(+), 35 deletions(-)
--
2.51.0
next reply other threads:[~2026-02-12 18:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 18:18 Paul Eggert [this message]
2026-02-12 18:18 ` [PATCH v3 1/4] Document max_align_t Paul Eggert
2026-02-26 12:41 ` Florian Weimer
2026-02-12 18:18 ` [PATCH v3 2/4] Document malloc alignment Paul Eggert
2026-02-26 12:53 ` Florian Weimer
2026-02-26 12:56 ` Florian Weimer
2026-02-26 13:17 ` Florian Weimer
2026-02-12 18:18 ` [PATCH v3 3/4] Say malloc (0) != NULL is now common; resection Paul Eggert
2026-02-26 13:15 ` Florian Weimer
2026-02-12 18:18 ` [PATCH v3 4/4] malloc: alignment might change in future versions Paul Eggert
2026-02-26 12:47 ` Florian Weimer
2026-02-26 18:41 ` Paul Eggert
2026-02-26 18:38 ` [PATCH 1/2] doc: document max_align_t effect on ABI Paul Eggert
2026-02-26 18:38 ` [PATCH 2/2] doc: document C23 changes to intmax_t Paul Eggert
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=20260212182031.107003-1-eggert@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).