public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	linux-man <linux-man@vger.kernel.org>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Subject: Re: [RFC] man7/system_data_types.7: Document [unsigned] __int128
Date: Thu, 1 Oct 2020 13:54:02 +0100	[thread overview]
Message-ID: <20201001125401.GF29000@arm.com> (raw)
In-Reply-To: <5ed7272e-1c81-d1f5-6a54-0fee4270199e@gmail.com>

The 10/01/2020 12:14, Alejandro Colomar via Gcc wrote:
> Here is the rendered intmax_t:
> 
> intmax_t
>       Include: <stdint.h>.  Alternatively, <inttypes.h>.
> 
>       A  signed  integer type capable of representing any value of any
>       signed integer type supported by the implementation.   According
>       to  the C language standard, it shall be capable of storing val-
>       ues in the range [INTMAX_MIN, INTMAX_MAX].
> 
>       The macro INTMAX_C() expands its argument to an integer constant
>       of type intmax_t.
> 
>       The  length  modifier  for  intmax_t  for  the printf(3) and the
>       scanf(3) families of functions is j; resulting commonly  in  %jd
>       or %ji for printing intmax_t values.
> 
>       Bugs:  intmax_t  is not large enough to represent values of type
>       __int128 in implementations where __int128 is defined  and  long
>       long is less than 128 bits wide.

or __int128 is not an integer type.

integer types are either standard or extended.
and __int128 is neither because it can be
larger than intmax_t and stdint.h does not
provide the necessary macros for it.

> 
>       Conforming to: C99 and later; POSIX.1-2001 and later.
> 
>       See also the uintmax_t type in this page.


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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01  9:24 [RFC] man7/system_data_types.7: Document [unsigned] __int128 Alejandro Colomar
2020-10-01  9:57 ` 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 [this message]
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=20201001125401.GF29000@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=colomar.6.4.3@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --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