On Thu, 1 Oct 2020 at 10:26, Alejandro Colomar via Gcc <gcc@xxxxxxxxxxx> wrote: > > 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'? Yes. > Is the GCC version correct? > > There's no implementation where 'long long' is 128 bits yet, right? 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. "According to GNU"? Should that be GCC? The GNU project doesn't have anything to say about it. Maybe just "When using GCC, it is supported only ..." > > 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. It doesn't conform to anything, shouldn't this say "This type is a GNU extension." or just "This type is an extension." ? > > Notes: This type is available without including any header. > > See also the intmax_t, intN_t and unsigned __int128 types in > this page. Why would this type refer to intmax_t?
