]> Savannah Git Hosting - gnulib.git/commitdiff
explicit_bzero: memset_explicit is standard
authorPaul Eggert <eggert@cs.ucla.edu>
Mon, 28 Nov 2022 04:52:04 +0000 (20:52 -0800)
committerPaul Eggert <eggert@cs.ucla.edu>
Tue, 29 Nov 2022 06:03:58 +0000 (22:03 -0800)
* doc/glibc-functions/explicit_bzero.texi:
Say that memset_explicit is preferred in new code.

ChangeLog
doc/glibc-functions/explicit_bzero.texi

index 2d29d1f646c424563c74eff06307faa77492be8f..ea76fef39981d366284608e3a006c1b73b75f7c2 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
 2022-11-27  Paul Eggert  <eggert@cs.ucla.edu>
 
+       explicit_bzero: memset_explicit is standard
+       * doc/glibc-functions/explicit_bzero.texi:
+       Say that memset_explicit is preferred in new code.
+
        read-file: use memset_explicit
        * lib/read-file.c (fread_file, read_file):
        Use memset_explicit instead of explicit_bzero.
index 31b4c9c011486d882534c9e976a1aa76e27c3c5b..a356659d272c3960f4c588b0c1ead9af30526d48 100644 (file)
@@ -24,6 +24,10 @@ question, the information that was in memory may still be available
 elsewhere on the machine.  Proper implementation of information
 erasure requires support from levels below C code.
 
+C23 specifies the function @code{memset_explicit}, which should be
+preferred to @code{explicit_bzero} in new code.
+@xref{memset_explicit}.
+
 Portability problems fixed by Gnulib:
 @itemize
 @item