public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <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 14:52:32 +0000 [thread overview] Message-ID: <bug-113770-4-MYqXIkkMkG@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Masahide Kashiwagi from comment #3) > I forgot to mention in my earlier post that these two programs work fine in > g++ 12. Because same thing as for clang applies there, _Float64 or _Float64x types aren't supported there in C++. gcc 12 and earlier only supports them in C. In GCC 13 and later, they are supported in C++ as well as distinct types, _Float{16,32,64,128} as underlying types for std::float{16,32,64,128}_t, and the x suffixed types just with minimal support (the compiler can mangle them among other things). But because they aren't standard C++, the library doesn't know about them and because they are distinct from long double etc. (again, intentional, because they should mangle differently), the long double etc. support in the STL headers doesn't work for those. > Also, at https://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html it says that > __float80 and _Float64x are 80-bit extended floating point numbers and are > available on x86. Has support for _Float64x been stopped? No, it has been added, but just in very limited way.
next prev parent reply other threads:[~2024-02-05 14:52 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 [this message] 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 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-MYqXIkkMkG@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).