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 target/99708] New: __SIZEOF_FLOAT128__ not defined on powerpc64le-linux Date: Mon, 22 Mar 2021 09:56:19 +0000 [thread overview] Message-ID: <bug-99708-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 Bug ID: 99708 Summary: __SIZEOF_FLOAT128__ not defined on powerpc64le-linux Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- For consistency with other targets, I think the rs6000 backend should predefine __SIZEOF_FLOAT128__ 16 __SIZEOF_IBM128__ 16 __SIZEOF_IEEE128__ 16 macros (each of them whenever __float128, __ibm128 or __ieee128 can be used given the current ABI and ISA options etc.). E.g. i386 backend has in i386-c.c cpp_define_formatted (parse_in, "__SIZEOF_FLOAT80__=%d", GET_MODE_SIZE (XFmode)); cpp_define (parse_in, "__SIZEOF_FLOAT128__=16"); Seems rs6000 predefines __FLOAT128__ macro instead when __float128 can be used and __FLOAT128_TYPE__ when __ibm128 and __ieee128 can be used.
next reply other threads:[~2021-03-22 9:56 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-22 9:56 jakub at gcc dot gnu.org [this message] 2021-03-22 16:42 ` [Bug target/99708] " segher at gcc dot gnu.org 2021-03-22 17:38 ` jakub at gcc dot gnu.org 2021-03-23 20:37 ` segher at gcc dot gnu.org 2021-03-24 10:17 ` jakub at gcc dot gnu.org 2021-03-24 14:50 ` redi at gcc dot gnu.org 2021-03-24 20:57 ` segher at gcc dot gnu.org 2021-03-24 21:13 ` redi at gcc dot gnu.org 2022-03-03 15:34 ` redi at gcc dot gnu.org 2022-03-03 15:37 ` redi at gcc dot gnu.org 2022-03-03 15:39 ` redi at gcc dot gnu.org 2022-03-03 16:30 ` segher at gcc dot gnu.org 2022-03-03 16:35 ` segher at gcc dot gnu.org 2022-03-03 17:05 ` jakub at gcc dot gnu.org 2022-03-03 17:52 ` jakub at gcc dot gnu.org 2022-03-03 18:01 ` jakub at gcc dot gnu.org 2022-03-03 18:07 ` jakub at gcc dot gnu.org 2022-03-03 23:03 ` segher at gcc dot gnu.org 2022-03-03 23:05 ` segher at gcc dot gnu.org 2022-03-04 9:28 ` jakub at gcc dot gnu.org 2022-03-04 13:46 ` segher at gcc dot gnu.org 2022-03-04 17:37 ` jakub at gcc dot gnu.org 2022-03-04 18:07 ` segher at gcc dot gnu.org 2022-03-04 18:07 ` segher at gcc dot gnu.org 2022-03-04 18:10 ` jakub at gcc dot gnu.org 2022-03-04 19:03 ` segher at gcc dot gnu.org 2022-03-04 19:30 ` jakub at gcc dot gnu.org 2022-03-04 20:22 ` segher at gcc dot gnu.org 2022-03-05 16:23 ` cvs-commit at gcc dot gnu.org 2022-03-06 1:16 ` cvs-commit at gcc dot gnu.org 2022-03-07 20:46 ` segher at gcc dot gnu.org 2022-03-10 9:31 ` cvs-commit at gcc dot gnu.org 2022-03-10 23:02 ` ebotcazou at gcc dot gnu.org 2022-03-10 23:10 ` jakub at gcc dot gnu.org 2022-03-11 23:43 ` cvs-commit at gcc dot gnu.org 2022-03-12 0:09 ` cvs-commit at gcc dot gnu.org 2022-05-20 2:36 ` bergner at gcc dot gnu.org 2023-04-15 2:58 ` cvs-commit at gcc dot gnu.org 2023-04-15 8:51 ` redi at gcc dot gnu.org 2023-04-15 8:52 ` redi at gcc dot gnu.org 2024-04-10 15:48 ` meissner 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-99708-4@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).