From: Collin Funk <collin.funk1@gmail.com>
Date: Tue, 30 Sep 2025 03:14:24 +0000 (-0700)
Subject: manual: Fix missing reference to the mmap function [BZ #20473]
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=e6cbc38bfbf143099600bd53d62eeea22280341f;p=thirdparty%2Fglibc.git

manual: Fix missing reference to the mmap function [BZ #20473]

Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
---

diff --git a/manual/setjmp.texi b/manual/setjmp.texi
index 7092a0dde2..6b044bd1f9 100644
--- a/manual/setjmp.texi
+++ b/manual/setjmp.texi
@@ -347,7 +347,7 @@ programs would fail.  Examples for such code include the calling
 sequences the GNU C compiler generates for calls to nested functions.
 Safe ways to allocate stacks correctly include using memory on the
 original thread's stack or explicitly allocating memory tagged for
-execution using (@pxref{Memory-mapped I/O}).
+execution using @code{mmap} (@pxref{Memory-mapped I/O}).
 
 @strong{Compatibility note}: The current Unix standard is very imprecise
 about the way the stack is allocated.  All implementations seem to agree