From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: gcc@gcc.gnu.org
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>
Subject: [RFC] man7/system_data_types.7: Document [unsigned] __int128
Date: Thu, 1 Oct 2020 11:24:45 +0200 [thread overview]
Message-ID: <f6179bab-bbad-22f7-0f87-c06988928ec2@gmail.com> (raw)
Hi,
I'm documenting the system data types in the man-pages,
and I was writing now about these types.
I'm showing below both the rendered output and the source I have right now.
Would you add anything to it?
And I have some questions:
Is 'signed __int128' a valid thing,
and if so is it completely equivalent to '__int128'?
Is the GCC version correct?
There's no implementation where 'long long' is 128 bits yet, right?
Thanks,
Alex
Rendered output:
[[
__int128
A signed integer type of a fixed width of exactly 128 bits.
According to GNU, it is supported only for targets which have an
integer mode wide enough to hold 128 bits.
Bugs: It is not possible to express an integer constant of type
__int128 in implementations where long long is less than 128
bits wide.
Conforming to: GCC 4.6.0 and later.
Notes: This type is available without including any header.
See also the intmax_t, intN_t and unsigned __int128 types in
this page.
[...]
unsigned __int128
An unsigned integer type of a fixed width of exactly 128 bits.
According to GNU, it is supported only for targets which have an
integer mode wide enough to hold 128 bits.
Bugs: It is not possible to express an integer constant of type
unsigned __int128 in implementations where unsigned long long is
less than 128 bits wide.
Conforming to: GCC 4.6.0 and later.
Notes: This type is available without including any header.
See also the __int128, uintmax_t and uintN_t types in this page.
]]
Source:
[[
.\"------------------------------------- __int128 ---------------------/
.TP
.I __int128
.RS
A signed integer type
of a fixed width of exactly 128 bits.
.PP
According to GNU,
it is supported only for targets which have
an integer mode wide enough to hold 128 bits.
.PP
Bugs:
It is not possible to express an integer constant of type
.I __int128
in implementations where
.I long long
is less than 128 bits wide.
.PP
Conforming to:
GCC 4.6.0 and later.
.PP
Notes:
This type is available without including any header.
.PP
See also the
.IR intmax_t ,
.IR int N _t
and
.I unsigned __int128
types in this page.
.RE
[...]
.\"------------------------------------- unsigned __int128 ------------/
.TP
.I unsigned __int128
.RS
An unsigned integer type
of a fixed width of exactly 128 bits.
.PP
According to GNU,
it is supported only for targets which have
an integer mode wide enough to hold 128 bits.
.PP
Bugs:
It is not possible to express an integer constant of type
.I unsigned __int128
in implementations where
.I unsigned long long
is less than 128 bits wide.
.PP
Conforming to:
GCC 4.6.0 and later.
.PP
Notes:
This type is available without including any header.
.PP
See also the
.IR __int128 ,
.I uintmax_t
and
.IR uint N _t
types in this page.
.RE
]]
next reply other threads:[~2020-10-01 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 9:24 Alejandro Colomar [this message]
2020-10-01 9:57 ` [RFC] man7/system_data_types.7: Document [unsigned] __int128 Jonathan Wakely
2020-10-01 10:14 ` Alejandro Colomar
2020-10-01 10:50 ` Jonathan Wakely
2020-10-01 11:24 ` Alejandro Colomar
2020-10-01 11:46 ` Jonathan Wakely
2020-10-01 12:54 ` Szabolcs Nagy
2020-10-01 13:22 ` Alejandro Colomar
2020-10-01 13:46 ` Jonathan Wakely
2020-10-01 17:31 ` Joseph Myers
2020-10-02 8:10 ` Alejandro Colomar
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=f6179bab-bbad-22f7-0f87-c06988928ec2@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=gcc@gcc.gnu.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).