public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi 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:32:17 +0000	[thread overview]
Message-ID: <bug-113770-4-9hD40ZJB9L@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 #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Masahide Kashiwagi from comment #0)
> Also no problem with clang++ 16.0.6.

That's because Clang doesn't support _Float64x or _Float64 at all.

Those names get defined as typedefs by libc:

# 214 "/usr/include/bits/floatn-common.h" 3 4
typedef float _Float32;
# 251 "/usr/include/bits/floatn-common.h" 3 4
typedef double _Float64;
# 268 "/usr/include/bits/floatn-common.h" 3 4
typedef double _Float32x;
# 285 "/usr/include/bits/floatn-common.h" 3 4
typedef long double _Float64x;

So when you use Clang, _Float64x is just another typedef for long double.

If you are happy to just use long double, then use long double. Don't try to
use extended floating point types that are not part of the C++ standard.

  parent reply	other threads:[~2024-02-05 14:32 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 [this message]
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
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-9hD40ZJB9L@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).