public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kashi at waseda dot jp" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113770] _Float64x support on g++ 13.2.0
Date: Mon, 05 Feb 2024 15:34:40 +0000 [thread overview]
Message-ID: <bug-113770-4-qdVYntktoK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113770-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113770
--- Comment #8 from Masahide Kashiwagi <kashi at waseda dot jp> ---
(In reply to Jakub Jelinek from comment #7)
> _Float64x certainly doesn't mean 80-bit. In C, it doesn't have to be
> supported at all (such as when IEEE double is the largest type supported by
> hw and/or emulation), or can be IEEE quad, 80-bit extended or whatever else.
> So, if you need only 80-bit and want an error otherwise, use __float80.
Thank you very much. This information was very important to me. I will stop
using _Float64x and consider using __float80 or long double.
next prev parent reply other threads:[~2024-02-05 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 14:17 [Bug c++/113770] New: " kashi at waseda dot jp
2024-02-05 14:29 ` [Bug c++/113770] " redi at gcc dot gnu.org
2024-02-05 14:32 ` redi at gcc dot gnu.org
2024-02-05 14:47 ` kashi at waseda dot jp
2024-02-05 14:52 ` jakub at gcc dot gnu.org
2024-02-05 15:08 ` kashi at waseda dot jp
2024-02-05 15:15 ` redi at gcc dot gnu.org
2024-02-05 15:16 ` jakub at gcc dot gnu.org
2024-02-05 15:34 ` kashi at waseda dot jp [this message]
2024-02-05 16:54 ` pinskia at gcc dot gnu.org
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=bug-113770-4-qdVYntktoK@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).