From: Paul Eggert Date: Mon, 28 Nov 2022 04:52:04 +0000 (-0800) Subject: explicit_bzero: memset_explicit is standard X-Git-Tag: v1.0~1953 X-Git-Url: https://gitweb.git.savannah.gnu.org/gitweb/?a=commitdiff_plain;h=c4d0e2a03fb2949189f7d74ad93bde8fbf7dbce8;p=gnulib.git explicit_bzero: memset_explicit is standard * doc/glibc-functions/explicit_bzero.texi: Say that memset_explicit is preferred in new code. --- diff --git a/ChangeLog b/ChangeLog index 2d29d1f646..ea76fef399 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,9 @@ 2022-11-27 Paul Eggert + 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. diff --git a/doc/glibc-functions/explicit_bzero.texi b/doc/glibc-functions/explicit_bzero.texi index 31b4c9c011..a356659d27 100644 --- a/doc/glibc-functions/explicit_bzero.texi +++ b/doc/glibc-functions/explicit_bzero.texi @@ -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