public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names Date: Wed, 24 Aug 2022 17:35:05 +0000 [thread overview] Message-ID: <bug-106652-4-FeyYj3zcIk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106652-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 --- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- Regarding mangling: I expect this change should fix bug 85518. General: I expect some glibc header changes might be appropriate, where they currently assume __FloatN keywords aren't supported in C++. And where glibc headers handle type-generic operations for C++ by defining appropriate overloaded functions in the headers, make sure the overloads for _Float128 work with both _Float128 and __float128 where supported and distinct, or otherwise adjust the headers as needed to handle both types. (Also, so far we don't have _Float16 support in glibc, and while it would be a sensible feature in principle, there would be issues to consider with the impact on minimum GCC versions for building glibc on relevant architectures, unless some kind of hack is used to allow _Float16 functions to be built and to get the correct ABI even when built with an older compiler. Requiring GCC 7 to build glibc for AArch64 and Arm might well be reasonable now; requiring GCC 12 for x86/x86_64 or GCC 13 for RISC-V probably not for a few years.)
next prev parent reply other threads:[~2022-08-24 17:35 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-16 17:14 [Bug c++/106652] New: " mpolacek at gcc dot gnu.org 2022-08-24 14:27 ` [Bug c++/106652] " jakub at gcc dot gnu.org 2022-08-24 14:49 ` jakub at gcc dot gnu.org 2022-08-24 16:56 ` jakub at gcc dot gnu.org 2022-08-24 17:35 ` joseph at codesourcery dot com [this message] 2022-08-25 12:51 ` jakub at gcc dot gnu.org 2022-08-25 12:55 ` jakub at gcc dot gnu.org 2022-08-25 14:39 ` jakub at gcc dot gnu.org 2022-09-09 9:44 ` jakub at gcc dot gnu.org 2022-09-09 18:12 ` jakub at gcc dot gnu.org 2022-09-10 10:20 ` jakub at gcc dot gnu.org 2022-09-10 10:22 ` jakub at gcc dot gnu.org 2022-09-10 17:28 ` jakub at gcc dot gnu.org 2022-09-10 17:31 ` jakub at gcc dot gnu.org 2022-09-10 18:13 ` jakub at gcc dot gnu.org 2022-09-27 6:18 ` cvs-commit at gcc dot gnu.org 2022-10-18 9:43 ` cvs-commit at gcc dot gnu.org 2022-10-19 9:26 ` cvs-commit at gcc dot gnu.org 2022-11-19 9:24 ` jakub at gcc dot gnu.org 2022-11-28 22:31 ` pinskia at gcc dot gnu.org 2022-12-09 15:20 ` pinskia at gcc dot gnu.org 2023-08-21 15:57 ` igorkuo at meta dot ua 2023-08-22 14:15 ` cvs-commit at gcc dot gnu.org 2023-08-22 14:16 ` cvs-commit 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-106652-4-FeyYj3zcIk@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).