bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: [PROPOSED 3/4] explicit_bzero: memset_explicit is standard
Date: Sun, 27 Nov 2022 20:55:42 -0800	[thread overview]
Message-ID: <20221128045543.1355731-4-eggert@cs.ucla.edu> (raw)
In-Reply-To: <20221128045543.1355731-1-eggert@cs.ucla.edu>

* doc/glibc-functions/explicit_bzero.texi:
Say that memset_explicit is preferred in new code.
---
 ChangeLog                               | 4 ++++
 doc/glibc-functions/explicit_bzero.texi | 4 ++++
 2 files changed, 8 insertions(+)

diff --git a/ChangeLog b/ChangeLog
index 2d29d1f646..ea76fef399 100644
--- 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.
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
-- 
2.37.2



  parent reply	other threads:[~2022-11-28  4:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28  4:55 [PROPOSED 0/4] memset_explicit patches Paul Eggert
2022-11-28  4:55 ` [PROPOSED 1/4] memset_explicit: new module Paul Eggert
2022-11-28 16:17   ` Bruno Haible
2022-11-28  4:55 ` [PROPOSED 2/4] read-file: use memset_explicit Paul Eggert
2022-11-28  4:55 ` Paul Eggert [this message]
2022-11-28  4:55 ` [PROPOSED 4/4] explicit_bzero: implement via memset_explicit Paul Eggert
2022-11-28 16:17   ` Bruno Haible
2022-11-29  6:06     ` Paul Eggert
2022-11-29  8:09       ` Bruno Haible
2022-11-28 10:15 ` [PROPOSED 0/4] memset_explicit patches Simon Josefsson via Gnulib discussion list
2022-11-28 16:04   ` Bruno Haible

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221128045543.1355731-4-eggert@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=bug-gnulib@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).