From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com, eggert@cs.ucla.edu, David.Laight@ACULAB.COM
Cc: linux-man@vger.kernel.org, gcc-patches@gcc.gnu.org,
libc-alpha@sourceware.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] system_data_types.7: void *: Add info about pointer artihmetic
Date: Fri, 2 Oct 2020 11:46:28 +0200 [thread overview]
Message-ID: <71ccc433-a5e4-92a7-6f09-d809c64b63f0@gmail.com> (raw)
In-Reply-To: <20201002094451.17997-1-colomar.6.4.3@gmail.com>
Hi Michael,
The 2/2 is a typo. This is a standalone patch.
Cheers,
Alex
On 2020-10-02 11:44, Alejandro Colomar wrote:
> Reported-by: Paul Eggert <eggert@cs.ucla.edu>
> Reported-by: David Laight <David.Laight@ACULAB.COM>
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
> ---
>
> Paul and David,
> Thanks for your input!
>
> Alex
>
>
> man7/system_data_types.7 | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
> index 6451782db..bc7d5a8a0 100644
> --- a/man7/system_data_types.7
> +++ b/man7/system_data_types.7
> @@ -1918,6 +1918,17 @@ A value of this type can't be dereferenced,
> as it would give a value of type
> .I void
> which is not possible.
> +Likewise, pointer arithmetic is not possible with this type.
> +However, in GNU C, poitner arithmetic is allowed
> +as an extension to the standard;
> +this is done by treating the size of a
> +.I void
> +or of a function as 1.
> +A consequence of this is that
> +.I sizeof
> +is also allowed on
> +.I void
> +and on function types, and returns 1.
> .PP
> The conversion specifier for
> .I void *
>
prev parent reply other threads:[~2020-10-02 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 9:44 [PATCH 2/2] system_data_types.7: void *: Add info about pointer artihmetic Alejandro Colomar
2020-10-02 9:46 ` Alejandro Colomar [this message]
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=71ccc433-a5e4-92a7-6f09-d809c64b63f0@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=eggert@cs.ucla.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).