From: Joseph Myers <joseph@codesourcery.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
Seija K. <doremylover123@gmail.com>, <libc-alpha@sourceware.org>
Subject: Re: Add restrict annotations to all functions that require it
Date: Tue, 6 Dec 2022 23:57:14 +0000 [thread overview]
Message-ID: <7f169d-e67d-ab82-e77f-a6f78a301495@codesourcery.com> (raw)
In-Reply-To: <082a5968-3f12-dc36-f50c-497820b0a4b2@gmail.com>
On Sat, 3 Dec 2022, Alejandro Colomar via Libc-alpha wrote:
> For example, this would be nonsense (and I honestly don't know what the
> compiler would understand from it):
>
> void broken(int *restrict a, int *b, int *c);
> void broken(int *a, int *restrict b, int *c);
Qualifiers on parameters in a function declarator that is not part of a
definition of that function have no semantic effect; restrict on function
parameters only has a semantic effect in the definition of the function.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-12-06 23:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 0:56 Add restrict annotations to all functions that require it Seija K. via Libc-alpha
2022-11-27 11:44 ` Mike Frysinger via Libc-alpha
2022-11-27 12:00 ` Alejandro Colomar via Libc-alpha
2022-12-03 14:32 ` Alejandro Colomar via Libc-alpha
2022-12-06 23:57 ` Joseph Myers [this message]
2022-12-07 11:59 ` Alejandro Colomar via Libc-alpha
2022-12-07 19:05 ` Joseph Myers
2022-11-27 12:04 ` Alejandro Colomar via Libc-alpha
2022-11-27 12:30 ` Alejandro Colomar via Libc-alpha
2022-11-27 12:39 ` Alejandro Colomar via Libc-alpha
2022-11-28 21:17 ` Joseph Myers
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://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7f169d-e67d-ab82-e77f-a6f78a301495@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=alx.manpages@gmail.com \
--cc=doremylover123@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=vapier@gentoo.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).