[PATCH v3 0/4] malloc doc fixes for alignment

[Paul Eggert]

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