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++/85518] ICE mangling _FloatN types Date: Thu, 25 Aug 2022 10:56:46 +0000 [thread overview] Message-ID: <bug-85518-4-LFyviqCpCH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-85518-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85518 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Actually not fully. While it adds mangling for _Float{16,32,64,128}, it doesn't add mangling for _Float{32,64,128}x. https://itanium-cxx-abi.github.io/cxx-abi/abi.html#mangling doesn't have anything for those and there is no need to add _Float{32,64,128}x support to the C++ FE right now. Perhaps the *x suffixed builtins should be C only?
next prev parent reply other threads:[~2022-08-25 10:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-85518-4@http.gcc.gnu.org/bugzilla/> 2022-08-25 10:23 ` jakub at gcc dot gnu.org 2022-08-25 10:56 ` jakub at gcc dot gnu.org [this message] 2022-09-27 6:18 ` cvs-commit at gcc dot gnu.org 2024-03-25 5:39 ` 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-85518-4-LFyviqCpCH@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).