linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
	gcc@gcc.gnu.org, libc-alpha@sourceware.org
Subject: Re: [PATCH v2 3/4] system_data_types.7: Add uint_fastN_t family of types
Date: Thu, 1 Oct 2020 17:25:01 +0200	[thread overview]
Message-ID: <ef23986d-d372-54f2-f23c-8af17cbcd667@gmail.com> (raw)
In-Reply-To: <20201001143203.98803-4-colomar.6.4.3@gmail.com>

Thanks, Alex. Applied.

On 10/1/20 4:32 PM, Alejandro Colomar wrote:
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
> ---
>  man7/system_data_types.7 | 80 ++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 80 insertions(+)
> 
> diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
> index c5d0b700d..c130b7256 100644
> --- a/man7/system_data_types.7
> +++ b/man7/system_data_types.7
> @@ -1348,6 +1348,86 @@ 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
> +Usually the fastest (see Notes) 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:
> +Where there is no single type that is fastest for all purposes,
> +the implementation may choose any type
> +with the required signedness and at least the minimum width.
> +.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
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2020-10-01 15:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 14:32 [PATCH v2 0/4] Document [u]int_fastN_t Alejandro Colomar
2020-10-01 14:32 ` [PATCH v2 1/4] system_data_types.7: Add int_fastN_t family of types Alejandro Colomar
2020-10-01 15:24   ` Michael Kerrisk (man-pages)
2020-10-01 14:32 ` [PATCH v2 2/4] 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 15:24   ` Michael Kerrisk (man-pages)
2020-10-01 14:32 ` [PATCH v2 3/4] system_data_types.7: Add uint_fastN_t family of types Alejandro Colomar
2020-10-01 15:25   ` Michael Kerrisk (man-pages) [this message]
2020-10-01 14:32 ` [PATCH v2 4/4] uint_fast8_t.3, uint_fast16_t.3, uint_fast32_t.3, uint_fast64_t.3, uint_fastN_t.3: New links to system_data_types(7) Alejandro Colomar
2020-10-01 15:25   ` Michael Kerrisk (man-pages)

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=ef23986d-d372-54f2-f23c-8af17cbcd667@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=colomar.6.4.3@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    /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).