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++/109884] __builtin_Xq returns _Float128 instead of __float128 Date: Wed, 17 May 2023 09:02:41 +0000 [thread overview] Message-ID: <bug-109884-4-yoFNOzMTwi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109884-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109884 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org Last reconfirmed| |2023-05-17 --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 55098 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55098&action=edit gcc14-pr109884.patch Untested fix. For ia64, I think it already uses float128t_type_node, for rs6000 as I wrote it is more difficult because it doesn't have the builtins but macros and in pa case, __float128 is the same as long double.
next prev parent reply other threads:[~2023-05-17 9:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-17 7:02 [Bug c++/109884] New: " g.peterhoff@t-online.de 2023-05-17 7:07 ` [Bug c++/109884] " pinskia at gcc dot gnu.org 2023-05-17 7:09 ` pinskia at gcc dot gnu.org 2023-05-17 7:17 ` g.peterhoff@t-online.de 2023-05-17 7:19 ` pinskia at gcc dot gnu.org 2023-05-17 7:20 ` redi at gcc dot gnu.org 2023-05-17 8:34 ` jakub at gcc dot gnu.org 2023-05-17 9:02 ` jakub at gcc dot gnu.org [this message] 2023-05-17 9:03 ` jakub at gcc dot gnu.org 2023-05-17 19:00 ` cvs-commit at gcc dot gnu.org 2023-05-17 19:27 ` cvs-commit at gcc dot gnu.org 2023-05-17 19:28 ` jakub 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-109884-4-yoFNOzMTwi@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).