From: Paul Floyd <pjfloyd@wanadoo.fr>
Date: Tue, 26 Nov 2024 07:08:37 +0000 (+0100)
Subject: Manual: C23 is now officially released
X-Git-Tag: VALGRIND_3_25_0~216
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=910519674ad97c98a9140ece3119e321774233d0;p=thirdparty%2Fvalgrind.git

Manual: C23 is now officially released
---

diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index 8ee5ba016..da7e81176 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