[Valgrind-developers] [valgrind] Manual: C23 is now officially released

[Paul F. <pa...@so...>]

https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=910519674ad97c98a9140ece3119e321774233d0

commit 910519674ad97c98a9140ece3119e321774233d0
Author: Paul Floyd <pj...@wa...>
Date:   Tue Nov 26 08:08:37 2024 +0100

    Manual: C23 is now officially released

Diff:
---
 docs/xml/manual-core.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index 8ee5ba0168..da7e811768 100644
--- a/docs/xml/manual-core.xml
+++ b/docs/xml/manual-core.xml
@@ -1793,9 +1793,9 @@ that can report errors, e.g. Memcheck, but not Cachegrind.</para>
       <option><![CDATA[--realloc-zero-bytes-frees=yes|no [default: yes for glibc no otherwise] ]]></option>
     </term>
     <listitem>
-      <para>The behaviour of <computeroutput>realloc()</computeroutput> is
-      implementation defined (in C17, in C23 it is likely to become
-      undefined). Valgrind tries to work in the same way as the
+      <para>The behaviour of <computeroutput>realloc()</computeroutput> with a size
+      of zero is implementation defined in C17 and undefined in C23.
+      Valgrind tries to work in the same way as the
       underlying system and C runtime library that it was configured and built on.
       However, if you use a different C runtime library then this default may be wrong.
       If the value is <option>yes</option> then <varname>realloc</varname> will