From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org,
Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Ulrich Drepper <drepper@redhat.com>,
Florian Weimer <fweimer@redhat.com>
Subject: [PATCH 07/22] lio_listio.3: SYNOPSIS: Use 'restrict' in prototypes
Date: Sat, 6 Mar 2021 00:50:51 +0100 [thread overview]
Message-ID: <20210305235105.177359-8-alx.manpages@gmail.com> (raw)
In-Reply-To: <20210305235105.177359-1-alx.manpages@gmail.com>
Both POSIX and glibc use 'restrict' in lio_listio().
However, POSIX is a bit more restrictive than glibc
for the second parameter.
Let's document the more restrictive POSIX variant.
$ man 3p lio_listio |sed -n '/^SYNOPSIS/,/;/p'
SYNOPSIS
#include <aio.h>
int lio_listio(int mode, struct aiocb *restrict const list[restrict],
int nent, struct sigevent *restrict sig);
$
.../glibc$ grep_glibc_prototype lio_listio
rt/aio.h:148:
extern int lio_listio (int __mode,
struct aiocb *const __list[__restrict_arr],
int __nent, struct sigevent *__restrict __sig)
__THROW __nonnull ((2));
.../glibc$
Cc: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Ulrich Drepper <drepper@redhat.com>
Cc: Florian Weimer <fweimer@redhat.com>
Cc: glibc <libc-alpha@sourceware.org>
Bug: glibc <https://sourceware.org/bugzilla/show_bug.cgi?id=16747>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
man3/lio_listio.3 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/man3/lio_listio.3 b/man3/lio_listio.3
index d89670f7c..d40ac89fb 100644
--- a/man3/lio_listio.3
+++ b/man3/lio_listio.3
@@ -28,8 +28,8 @@ lio_listio \- initiate a list of I/O requests
.nf
.B "#include <aio.h>"
.PP
-.BI "int lio_listio(int " mode ", struct aiocb *const " aiocb_list [],
-.BI " int " nitems ", struct sigevent *" sevp );
+.BI "int lio_listio(int " mode ", struct aiocb *restrict const " aiocb_list [restrict],
+.BI " int " nitems ", struct sigevent *restrict " sevp );
.PP
Link with \fI\-lrt\fP.
.fi
--
2.30.1.721.g45526154a5
next prev parent reply other threads:[~2021-03-05 23:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 23:50 [PATCH 00/22] man3: SYNOPSIS: Use 'restrict' in prototypes (batch 3) Alejandro Colomar
2021-03-05 23:50 ` [PATCH 01/22] getservent_r.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-03-05 23:50 ` [PATCH 02/22] getsubopt.3: " Alejandro Colomar
2021-03-05 23:50 ` [PATCH 03/22] glob.3: " Alejandro Colomar
2021-03-05 23:50 ` [PATCH 04/22] iconv.3: " Alejandro Colomar
2021-03-05 23:50 ` [PATCH 05/22] inet_ntop.3: " Alejandro Colomar
2021-03-05 23:50 ` [PATCH 06/22] inet_pton.3: " Alejandro Colomar
2021-03-05 23:50 ` Alejandro Colomar [this message]
2021-03-05 23:50 ` [PATCH 08/22] makecontext.3: " Alejandro Colomar
2021-03-05 23:50 ` [PATCH 09/22] malloc_hook.3: SYNOPSIS: Use 'volatile' " Alejandro Colomar
2021-03-05 23:50 ` [PATCH 10/22] mbrlen.3: SYNOPSIS: Use 'restrict' " Alejandro Colomar
2021-03-05 23:50 ` [PATCH 11/22] mbrtowc.3: " Alejandro Colomar
2021-03-05 23:50 ` [PATCH 12/22] mbsnrtowcs.3: " Alejandro Colomar
2021-03-05 23:50 ` [PATCH 13/22] mbsrtowcs.3: " Alejandro Colomar
2021-03-05 23:50 ` [PATCH 14/22] mbstowcs.3: " Alejandro Colomar
2021-03-05 23:50 ` [PATCH 15/22] mbtowc.3: " Alejandro Colomar
2021-03-05 23:51 ` [PATCH 16/22] mempcpy.3: " Alejandro Colomar
2021-03-05 23:51 ` [PATCH 17/22] mq_getattr.3: " Alejandro Colomar
2021-03-05 23:51 ` [PATCH 18/22] mq_receive.3: " Alejandro Colomar
2021-03-05 23:51 ` [PATCH 19/22] posix_spawn.3: " Alejandro Colomar
2021-03-05 23:51 ` [PATCH 20/22] " Alejandro Colomar
2021-03-05 23:51 ` [PATCH 21/22] printf.3: SYNOPSIS: Use 'restrict' in prototypes; ffix too Alejandro Colomar
2021-03-05 23:51 ` [PATCH 22/22] pthread_attr_setguardsize.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-03-07 10:20 ` [PATCH 00/22] man3: SYNOPSIS: Use 'restrict' in prototypes (batch 3) Michael Kerrisk (man-pages)
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210305235105.177359-8-alx.manpages@gmail.com \
--to=alx.manpages@gmail.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=drepper@redhat.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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).