public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com
Cc: colomar.6.4.3@gmail.com, linux-man@vger.kernel.org,
	libc-alpha@sourceware.org, gcc@gcc.gnu.org
Subject: [PATCH 07/16] system_data_types.7: Add uint_fastN_t family of types
Date: Thu,  1 Oct 2020 12:15:51 +0200	[thread overview]
Message-ID: <20201001101559.77163-8-colomar.6.4.3@gmail.com> (raw)
In-Reply-To: <20201001101559.77163-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 07de6417f..e3ebc2270 100644
--- a/man7/system_data_types.7
+++ b/man7/system_data_types.7
@@ -1282,6 +1282,85 @@ See also:
 .BR getpwnam (2),
 .BR credentials (7)
 .RE
+.\"------------------------------------- uint_fastN_t -----------------/
+.TP
+.IR uint_fast N _t
+.RS
+Include:
+.IR <stdint.h> .
+Alternatively,
+.IR <inttypes.h> .
+.PP
+.IR uint_fast8_t ,
+.IR uint_fast16_t ,
+.IR uint_fast32_t ,
+.I uint_fast64_t
+.PP
+The fastest unsigned integer type
+of a width of at least 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 [0,
+.BR UINT_FAST N _MAX ],
+substituting N by the appropriate number.
+.PP
+The length modifiers for the
+.IR uint_fast N _t
+types for the
+.BR printf (3)
+family of functions
+are expanded by macros of the forms
+.BR PRIuFAST N,
+.BR PRIoFAST N,
+.BR PRIxFAST N
+and
+.BR PRIXFAST N
+(defined in
+.IR <inttypes.h> );
+resulting for example in
+.B %"PRIuFAST32"
+or
+.B %"PRIxFAST32"
+for printing
+.I uint_fast32_t
+values.
+The length modifiers for the
+.IR uint_fast N _t
+types for the
+.BR scanf (3)
+family of functions
+are expanded by macros of the forms
+.BR SCNuFAST N,
+.BR SCNoFAST N,
+.BR SCNxFAST N
+and
+.BR SCNXFAST N
+(defined in
+.IR <inttypes.h> );
+resulting for example in
+.B %"SCNuFAST16"
+or
+.B %"SCNxFAST16"
+for scanning
+.I uint_fast16_t
+values.
+.PP
+Conforming to:
+C99 and later; POSIX.1-2001 and later.
+.PP
+Notes:
+Some of these types may be optimized for size
+instead of raw performance.
+.PP
+See also the
+.IR int_fast N _t ,
+.IR int_least N _t ,
+.IR int N _t ,
+.IR uint_least N _t
+and
+.IR uint N _t
+types in this page.
+.RE
 .\"------------------------------------- uintmax_t --------------------/
 .TP
 .I uintmax_t
-- 
2.28.0


  parent reply	other threads:[~2020-10-01 10:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 10:15 [PATCH 00/16] Fixes; Document remaining stdint.h types Alejandro Colomar
2020-10-01 10:15 ` [PATCH 01/16] malloc_get_state.3: ffix Alejandro Colomar
2020-10-01 11:32   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 02/16] system_data_types.7: srcfix Alejandro Colomar
2020-10-01 11:33   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 03/16] " Alejandro Colomar
2020-10-01 11:33   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 04/16] " Alejandro Colomar
2020-10-01 11:34   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 05/16] system_data_types.7: Add int_fastN_t family of types Alejandro Colomar
2020-10-01 11:07   ` Jonathan Wakely
2020-10-01 11:15     ` Alejandro Colomar
2020-10-01 11:27       ` Jonathan Wakely
2020-10-01 14:16         ` Alejandro Colomar
2020-10-01 15:13     ` Alejandro Colomar
2020-10-01 10:15 ` [PATCH 06/16] int_fast8_t.3, int_fast16_t.3, int_fast32_t.3, int_fast64_t.3, int_fastN_t.3: New links to system_data_types(7) Alejandro Colomar
2020-10-01 10:15 ` Alejandro Colomar [this message]
2020-10-01 10:15 ` [PATCH 08/16] uint_fast8_t.3, uint_fast16_t.3, uint_fast32_t.3, uint_fast64_t.3, uint_fastN_t.3: " Alejandro Colomar
2020-10-01 10:15 ` [PATCH 09/16] system_data_types.7: Add int_leastN_t family of types Alejandro Colomar
2020-10-01 10:15 ` [PATCH 10/16] int_least8_t.3, int_least16_t.3, int_least32_t.3, int_least64_t.3, int_leastN_t.3: New links to system_data_types(7) Alejandro Colomar
2020-10-01 10:15 ` [PATCH 11/16] system_data_types.7: Add uint_leastN_t family of types Alejandro Colomar
2020-10-01 10:15 ` [PATCH 12/16] uint_least8_t.3, uint_least16_t.3, uint_least32_t.3, uint_least64_t.3, uint_leastN_t.3: New links to system_data_types(7) Alejandro Colomar
2020-10-01 10:15 ` [PATCH 13/16] system_data_types.7: Add 'intptr_t' Alejandro Colomar
2020-10-01 11:35   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 14/16] intptr_t.3: New link to system_data_types(7) Alejandro Colomar
2020-10-01 11:35   ` Michael Kerrisk (man-pages)
2020-10-01 10:15 ` [PATCH 15/16] system_data_types.7: Add 'uintptr_t' Alejandro Colomar
2020-10-01 11:35   ` Michael Kerrisk (man-pages)
2020-10-01 10:16 ` [PATCH 16/16] uintptr_t.3: New link to system_data_types(7) Alejandro Colomar
2020-10-01 11:35   ` Michael Kerrisk (man-pages)
2020-10-01 11:32 ` [PATCH 00/16] Fixes; Document remaining stdint.h types Michael Kerrisk (man-pages)
2020-10-01 11:41   ` Alejandro Colomar
2020-10-01 11:50     ` Michael Kerrisk (man-pages)
2020-10-01 11:51       ` 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=20201001101559.77163-8-colomar.6.4.3@gmail.com \
    --to=colomar.6.4.3@gmail.com \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).