From: Paul Eggert <eggert@cs.ucla.edu>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Alejandro Colomar via Libc-alpha <libc-alpha@sourceware.org>,
linux-man@vger.kernel.org, gcc-patches@gcc.gnu.org,
mtk.manpages@gmail.com
Subject: Re: [PATCH 1/4] system_data_types.7: Add '__int128'
Date: Fri, 2 Oct 2020 12:54:13 -0700 [thread overview]
Message-ID: <daa5c152-0462-19d2-d327-0042f405a40c@cs.ucla.edu> (raw)
In-Reply-To: <bcce5f89-6682-e089-d129-43c36fe3f392@gmail.com>
On 10/2/20 12:01 PM, Alejandro Colomar wrote:
> If you propose not to document the stdint types either,
This is not a stdint.h issue. __int128 is not in stdint.h and is not a system
data type in any real sense; it's purely a compiler issue. Besides, do we start
repeating the GCC manual too, while we're at it? At some point we need to
restrain ourselves and stay within the scope of the man pages.
PS. Have you ever tried to use __int128 in real code? I have, to my regret. It's
a portability and bug minefield and should not be used unless you really know
what you're doing, which most people do not.
next prev parent reply other threads:[~2020-10-02 19:54 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
2020-10-02 17:52 ` Paul Eggert
2020-10-02 19:01 ` Alejandro Colomar
2020-10-02 19:54 ` Paul Eggert [this message]
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=daa5c152-0462-19d2-d327-0042f405a40c@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=colomar.6.4.3@gmail.com \
--cc=fweimer@redhat.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.