From: Gabriel Ravier <gabravier@gmail.com>
To: gcc@gcc.gnu.org
Subject: Re: IEEE Interchange floating point and extended floating point for C++
Date: Thu, 11 Mar 2021 15:02:29 +0100 [thread overview]
Message-ID: <8bf4aad6-390d-3735-5c8c-457f036c379f@gmail.com> (raw)
In-Reply-To: <CAH6eHdRwhyUzVPZdY1Qdc-5wJdmEtHxN5gh8zi49QXDXr7x8-w@mail.gmail.com>
On 3/11/21 1:56 PM, Jonathan Wakely via Gcc wrote:
> On Thu, 11 Mar 2021 at 09:43, Kito Cheng via Gcc <gcc@gcc.gnu.org> wrote:
>> Hi:
>>
>> Would it be possible to support interchange floating point and/or
>> extended floating point for C++, which is introduced by ISO/IEC TS
>> 18661-3?
>>
>> I've read the note about C++ support from the initial commit log[1],
>> so I know there is some concern about C++ support for that, is it
>> possible to enable that for C++ like a language extension for C++?
>>
>> The main demand comes from the data type for half-precision, ISO/IEC
>> TS 18661-3 is the only common spec which supports half-precision and
>> both GCC and clang are supported.
>>
>> However it can't be used on C++ for GCC, so it's hard to use that as a
>> workable solution for half-precision data types.
>>
>> Or maybe ISO/IEC JTC1 SC22 WG14 N2016[2] is a better way for
>> half-precision data types?
> See https://wg21.link/p1467 and https://wg21.link/p1467 for the
> relevant C++ proposals.
Isn't that the same link two times ?
next prev parent reply other threads:[~2021-03-11 14:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 9:07 Kito Cheng
2021-03-11 12:56 ` Jonathan Wakely
2021-03-11 14:02 ` Gabriel Ravier [this message]
2021-03-11 15:14 ` Jonathan Wakely
2021-03-11 15:14 ` Jonathan Wakely
2021-03-12 6:50 ` Kito Cheng
2021-03-11 14:26 ` Joseph Myers
2021-03-12 7:17 ` Kito Cheng
2021-03-12 9:27 ` Jonathan Wakely
2021-03-12 11:42 ` Sjoerd Meijer
2021-03-12 12:31 ` Jonathan Wakely
2021-03-12 17:49 ` Joseph Myers
2021-03-12 18:14 ` Joseph Myers
2021-03-12 20:53 ` Jonathan Wakely
2021-03-12 21:55 ` Joseph Myers
2021-03-12 22:03 ` Jonathan Wakely
2021-03-15 10:16 ` Sjoerd Meijer
2021-03-15 10:20 ` Jonathan Wakely
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=8bf4aad6-390d-3735-5c8c-457f036c379f@gmail.com \
--to=gabravier@gmail.com \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).