]> git.ipfire.org Git - thirdparty/valgrind.git/commitdiff
Manual: C23 is now officially released
authorPaul Floyd <pjfloyd@wanadoo.fr>
Tue, 26 Nov 2024 07:08:37 +0000 (08:08 +0100)
committerPaul Floyd <pjfloyd@wanadoo.fr>
Tue, 26 Nov 2024 07:08:37 +0000 (08:08 +0100)
docs/xml/manual-core.xml

index 8ee5ba01681f4db495800503a6d74a5ef1d7fc3e..da7e8117681aa0b0773e9a16a41d4b63422f44b7 100644 (file)
@@ -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