From: Florian Weimer <fweimer@redhat.com>
To: Alejandro Colomar via Libc-alpha <libc-alpha@sourceware.org>
Cc: mtk.manpages@gmail.com,
Alejandro Colomar <colomar.6.4.3@gmail.com>,
linux-man@vger.kernel.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/4] system_data_types.7: Add '__int128'
Date: Fri, 02 Oct 2020 13:47:03 +0200 [thread overview]
Message-ID: <87eemg97ew.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20201001163443.106933-2-colomar.6.4.3@gmail.com> (Alejandro Colomar via Libc-alpha's message of "Thu, 1 Oct 2020 18:34:41 +0200")
* Alejandro Colomar via Libc-alpha:
> +the compiler is able to generate efficient code for 128-bit arithmetic".
Stray "?
> +.PP
> +See also the
> +.IR intmax_t ,
> +.IR int N _t
I think it's surprising that intmax_t can be smaller than __int128 (and
usually is, I think), so that's probably worth mentioning. Assuming
that we want to document __int128 at all as part of the man-pages
project.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-10-02 11:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 16:34 [PATCH 0/4] Document 128-bit types Alejandro Colomar
2020-10-01 16:34 ` [PATCH 1/4] system_data_types.7: Add '__int128' Alejandro Colomar
2020-10-02 11:47 ` Florian Weimer [this message]
2020-10-02 17:52 ` Paul Eggert
2020-10-02 19:01 ` Alejandro Colomar
2020-10-02 19:54 ` Paul Eggert
2020-10-02 20:03 ` Alejandro Colomar
2020-10-02 20:19 ` Paul Eggert
2020-10-02 23:44 ` Alejandro Colomar
2020-10-02 23:53 ` Paul Eggert
2020-10-05 7:12 ` Florian Weimer
2020-10-07 6:53 ` Michael Kerrisk (man-pages)
2020-10-07 6:57 ` Florian Weimer
2020-10-01 16:34 ` [PATCH 2/4] __int128.3: New link to system_data_types(7) Alejandro Colomar
2020-10-01 16:34 ` [PATCH 3/4] system_data_types.7: Add 'unsigned __int128' Alejandro Colomar
2020-10-01 16:34 ` [PATCH 4/4] unsigned-__int128.3: New link to system_data_types(7) Alejandro Colomar
2020-10-02 12:28 ` [PATCH v2 0/4] Document 128-bit types Alejandro Colomar
2020-10-02 12:28 ` [PATCH v2 1/4] system_data_types.7: Add '__int128' Alejandro Colomar
2020-10-02 12:28 ` [PATCH v2 2/4] __int128.3: New link to system_data_types(7) Alejandro Colomar
2020-10-02 12:28 ` [PATCH v2 3/4] system_data_types.7: Add 'unsigned __int128' Alejandro Colomar
2020-10-02 12:28 ` [PATCH v2 4/4] unsigned-__int128.3: New link to system_data_types(7) 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=87eemg97ew.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=colomar.6.4.3@gmail.com \
--cc=gcc-patches@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.