From: Alejandro Colomar <alx+linux-man@kernel.org>
To: Christopher Bazley <chris.bazley.wg14@gmail.com>
Cc: linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
Sam James <sam@gentoo.org>, Carlos O'Donell <carlos@redhat.com>,
"Joseph S. Myers" <josmyers@redhat.com>,
Martin Uecker <uecker@tugraz.at>
Subject: Re: [PATCH] man/: SYNOPSIS: Remove GNU forward-declarations of parameters for lengths of array parameters
Date: Fri, 23 Oct 2026 14:11:12 +0200 [thread overview]
Message-ID: <attOh6Rt65MavbuK@debian> (raw)
In-Reply-To: <atpnWiYQzs_HZ1Q7@debian>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
> Date: 2026-10-22 21:54:09+0200
> From: Alejandro Colomar <alx+linux-man@kernel.org>
>
> > Date: 2026-10-22 18:29:31+0100
> > From: Christopher Bazley <chris.bazley.wg14@gmail.com>
> >
[...]
> > but the fact that there are no useful ISO C
> > semantics for parameters of pointer type declared using array syntax
> > weakens my concern. (If the parameters actually had variably-modified types
> > then the change would be far worse, from my point of view, because the
> > parameter types would no longer be expressed correctly.)
>
> We don't care about what ISO C says. GNU C clearly assigns semantics to
> array parameters, and that means we have to be careful about them here.
> If this can result in sanitizers breaking code, it is something to be
> careful about. Moreover, I hope ISO C eventually catches up.
Moreover, there's GCC discussing at the moment a patch of mine to have
_Countof(parameter) work, which would be an even larger risk: it would
produce different values in code, and not just sanitizers aborting some
program.
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-10-23 12:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 16:44 [PATCH] man/: SYNOPSIS: Remove GNU forward-declarations of parameters for lengths of array parameters Alejandro Colomar
2026-10-22 17:11 ` Martin Uecker
2026-10-22 20:01 ` Alejandro Colomar
2026-10-22 20:27 ` Alejandro Colomar
2026-10-22 17:37 ` Christopher Bazley
[not found] ` <CAEHU8x9jET+vcrR0NpDz6t57egQG8TZqx5XtV52srH9ZRvdxSQ@mail.gmail.com>
2026-10-22 19:54 ` Alejandro Colomar
2026-10-23 11:53 ` Michael Kerrisk (man7.org)
2026-10-23 12:42 ` Alejandro Colomar
2026-10-23 15:51 ` Christopher Bazley
2026-10-24 12:45 ` Michael Kerrisk (man7.org)
2026-10-24 13:38 ` Alejandro Colomar
2026-10-24 16:16 ` Christopher Bazley
2026-10-24 16:37 ` Alejandro Colomar
2026-10-24 18:11 ` Martin Uecker
2026-10-25 6:59 ` Alejandro Colomar
2026-10-25 7:22 ` Martin Uecker
2026-10-25 7:38 ` Alejandro Colomar
2026-10-25 8:29 ` G. Branden Robinson
2026-10-25 8:40 ` Martin Uecker
2026-10-25 8:57 ` Alejandro Colomar
2026-10-25 9:05 ` Martin Uecker
2026-10-23 12:11 ` Alejandro Colomar [this message]
2026-10-22 22:03 ` Mark Harris
2026-10-23 9:43 ` Alejandro Colomar
2026-10-23 19:32 ` Mark Harris
2026-10-23 20:06 ` Alejandro Colomar
2026-10-24 7:53 ` Martin Uecker
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=attOh6Rt65MavbuK@debian \
--to=alx+linux-man@kernel.org \
--cc=carlos@redhat.com \
--cc=chris.bazley.wg14@gmail.com \
--cc=josmyers@redhat.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=sam@gentoo.org \
--cc=uecker@tugraz.at \
/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