From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <colomar.6.4.3@gmail.com>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org,
gcc@gcc.gnu.org, colomar.6.4.3@gmail.org
Subject: [PATCH v2 5/8] system_data_types.7: Add intN_t family of types
Date: Tue, 29 Sep 2020 12:30:27 +0200 [thread overview]
Message-ID: <20200929103028.56566-6-colomar.6.4.3@gmail.com> (raw)
In-Reply-To: <20200929082524.49529-1-colomar.6.4.3@gmail.com>
Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
---
man7/system_data_types.7 | 79 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 79 insertions(+)
diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
index 2e7aca7d2..9b8244649 100644
--- a/man7/system_data_types.7
+++ b/man7/system_data_types.7
@@ -399,6 +399,85 @@ See also the
.I uintmax_t
type in this page.
.RE
+.\"------------------------------------- intN_t -----------------------/
+.TP
+.IR int N _t
+.RS
+.br
+Include:
+.IR <stdint.h> .
+Alternatively,
+.IR <inttypes.h> .
+.PP
+.IR int8_t ", " int16_t ", " int32_t ", " int64_t
+.PP
+A signed integer type
+of a fixed width of exactly N bits,
+N being the value specified in its type name.
+According to the C language standard, they shall be
+capable of storing values in the range
+.RB [ INT N _MIN ,
+.BR INT N _MAX ],
+substituting N by the appropriate number.
+.PP
+According to POSIX,
+.IR int8_t ", " int16_t
+and
+.I int32_t
+are required;
+.I int64_t
+is only required in implementations that provide integer types
+with width 64;
+and all other types of this form are optional.
+.PP
+The length modifiers for the
+.IR int N _t
+types for the
+.BR printf (3)
+family of functions
+are expanded by macros of the forms
+.BR PRId N
+and
+.BR PRIi N
+(defined in
+.IR <inttypes.h> );
+resulting for example in
+.B %"PRId64"
+or
+.B %"PRIi64"
+for printing
+.I int64_t
+values.
+The length modifiers for the
+.IR int N _t
+types for the
+.BR scanf (3)
+family of functions
+are expanded by macros of the forms
+.BR SCNd N
+and
+.BR SCNi N,
+(defined in
+.IR <inttypes.h> );
+resulting for example in
+.B %"SCNd8"
+or
+.B %"SCNi8"
+for scanning
+.I int8_t
+values.
+.PP
+Conforming to: C99 and later; POSIX.1-2001 and later.
+.PP
+See also the
+.IR __int128 ,
+.IR intmax_t ,
+.IR uint N _t ,
+.I uintmax_t
+and
+.I unsigned __int128
+types in this page.
+.RE
.\"------------------------------------- lconv ------------------------/
.TP
.I lconv
--
2.28.0
next prev parent reply other threads:[~2020-09-29 10:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 8:25 [PATCH 0/8] Add some <stdint.h> types Alejandro Colomar
2020-09-29 10:30 ` [PATCH v2 " Alejandro Colomar
2020-09-29 10:34 ` Alejandro Colomar
2020-09-29 10:30 ` [PATCH v2 1/8] system_data_types.7: Add 'intmax_t' Alejandro Colomar
2020-09-29 10:30 ` [PATCH v2 2/8] intmax_t.3: New link to system_data_types(7) Alejandro Colomar
2020-09-29 10:30 ` [PATCH v2 3/8] system_data_types.7: Add 'uintmax_t' Alejandro Colomar
2020-09-29 10:30 ` [PATCH v2 4/8] uintmax_t.3: New link to system_data_types(7) Alejandro Colomar
2020-09-29 10:30 ` Alejandro Colomar [this message]
2020-09-29 10:30 ` [PATCH v2 6/8] int8_t.3, int16_t.3, int32_t.3, int64_t.3, intN_t.3: New links " Alejandro Colomar
2020-09-29 10:30 ` [PATCH v2 7/8] system_data_types.7: Add uintN_t family of types Alejandro Colomar
2020-09-29 10:30 ` [PATCH v2 8/8] uint8_t.3, uint16_t.3, uint32_t.3, uint64_t.3, uintN_t.3: New links to system_data_types(7) Alejandro Colomar
2020-09-29 11:50 ` [PATCH 0/8] Add some <stdint.h> types Michael Kerrisk (man-pages)
2020-09-29 12:24 ` 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=20200929103028.56566-6-colomar.6.4.3@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=colomar.6.4.3@gmail.org \
--cc=gcc@gcc.gnu.org \
--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 NNTP newsgroup(s).