public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/112498] std::is_convertible<float, _Float16>::value returns false Date: Sun, 12 Nov 2023 22:35:14 +0000 [thread overview] Message-ID: <bug-112498-4-7MrVMwruuQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112498-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112498 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED Component|libstdc++ |c++ See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=111842 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- No. ``` _Float16 f(float a) { return a; } ``` is invalid C++23 code. <source>:3:10: warning: converting to '_Float16' from 'float' with greater conversion rank Maybe we should add this to the FAQ because we get a question about implicit conversion from _Float16 to float a few times now. See https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1467r4.html#implicit Which is the C++ paper which adds the extended floating point types and GCC implements it full. Just as an extension allows the conversion (with a warning) but since we cannot have different behavior for sfinae and concepts with -pedantic/-pedantic-errors std::is_convertible needs to return false.
next prev parent reply other threads:[~2023-11-12 22:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-12 22:28 [Bug libstdc++/112498] New: " josopait at goopax dot com 2023-11-12 22:35 ` pinskia at gcc dot gnu.org [this message] 2023-11-12 23:56 ` [Bug c++/112498] " josopait at goopax dot com 2023-11-13 10:10 ` redi at gcc dot gnu.org 2023-11-14 9:55 ` cvs-commit at gcc dot gnu.org 2023-11-14 10:32 ` redi 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-112498-4-7MrVMwruuQ@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).