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:08:58 +0000 [thread overview] Message-ID: <bug-113770-4-c3JYht2CjX@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 #5 from Masahide Kashiwagi <kashi at waseda dot jp> --- Thank you very much. I understand that g++ 13 no longer supports _Float64x in a very limited way. Does this mean that if I want to use 80-bit extended floating point numbers in g++ 13 or later, is it best to use long double? Since long double may not be 80-bit on non-x86 architectures, I wanted to use _Float64x or __float80, which are clearly 80-bit, if possible.
next prev parent reply other threads:[~2024-02-05 15:08 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 [this message] 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 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-c3JYht2CjX@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: linkBe 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).