public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux
Date: Sun, 06 Mar 2022 01:16:24 +0000 [thread overview]
Message-ID: <bug-99708-4-aSivXxnpVc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99708-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708
--- Comment #29 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Michael Meissner
<meissner@gcc.gnu.org>:
https://gcc.gnu.org/g:641b407763ecfee5d4ac86d8ffe9eb1eeea5fd10
commit r10-10486-g641b407763ecfee5d4ac86d8ffe9eb1eeea5fd10
Author: Michael Meissner <meissner@linux.ibm.com>
Date: Sat Mar 5 20:11:38 2022 -0500
Define __SIZEOF_FLOAT128__ and __SIZEOF_IBM128__.
Define the sizes of the PowerPC specific types __float128 and __ibm128 if
those
types are enabled.
This patch will define __SIZEOF_IBM128__ and __SIZEOF_FLOAT128__ if their
respective types are created in the compiler. Currently, this means both
of
these will be defined if float128 support is enabled. But at some point in
the future, __ibm128 could be enabled without enabling float128 support and
__SIZEOF_IBM128__ would be defined.
2022-03-05 Michael Meissner <meissner@the-meissners.org>
gcc/
PR target/99708
* config/rs6000/rs6000-c.c (rs6000_cpu_cpp_builtins): Define
__SIZEOF_IBM128__ if the IBM 128-bit long double type is created.
Define __SIZEOF_FLOAT128__ if the IEEE 128-bit floating point type
is created. Backport change to master branch on 2022-02-17.
gcc/testsuite/
PR target/99708
* gcc.target/powerpc/pr99708.c: New test. Backport change to
master branch on 2022-02-17.
next prev parent reply other threads:[~2022-03-06 1:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 9:56 [Bug target/99708] New: " jakub at gcc dot gnu.org
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 [this message]
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-aSivXxnpVc@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: link
Be 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).