public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64
Date: Wed, 21 Jun 2023 17:41:33 +0000 [thread overview]
Message-ID: <bug-101002-4-su7dXpMQ7l@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101002-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002
--- Comment #6 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #5)
> The creation of the __ibm128 type is guarded by:
>
> if (TARGET_LONG_DOUBLE_128 && (!TARGET_IEEEQUAD || TARGET_FLOAT128_TYPE))
>
> Since the __ibm128 type is independent of what long double defaults to, I
> assume the fix is to just remove the TARGET_LONG_DOUBLE_128 test giving us:
>
> if (!TARGET_IEEEQUAD || TARGET_FLOAT128_TYPE)
I'm going to test the following to see whether anything bad falls out:
--- a/gcc/config/rs6000/rs6000-builtin.cc
+++ b/gcc/config/rs6000/rs6000-builtin.cc
@@ -710,9 +710,9 @@ rs6000_init_builtins (void)
For IEEE 128-bit floating point, always create the type __ieee128. If
the
user used -mfloat128, rs6000-c.cc will create a define from __float128 to
__ieee128. */
- if (TARGET_LONG_DOUBLE_128 && (!TARGET_IEEEQUAD || TARGET_FLOAT128_TYPE))
+ if (!TARGET_IEEEQUAD || TARGET_FLOAT128_TYPE)
{
- if (!TARGET_IEEEQUAD)
+ if (TARGET_LONG_DOUBLE_128 && !TARGET_IEEEQUAD)
ibm128_float_type_node = long_double_type_node;
else
{
next prev parent reply other threads:[~2023-06-21 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 20:18 [Bug testsuite/101002] New: " meissner at gcc dot gnu.org
2021-06-10 15:17 ` [Bug testsuite/101002] " bergner at gcc dot gnu.org
2021-06-11 20:54 ` segher at gcc dot gnu.org
2021-06-11 20:55 ` segher at gcc dot gnu.org
2023-06-20 21:20 ` bergner at gcc dot gnu.org
2023-06-21 17:30 ` bergner at gcc dot gnu.org
2023-06-21 17:41 ` bergner at gcc dot gnu.org [this message]
2023-06-21 20:31 ` bergner at gcc dot gnu.org
2023-06-21 20:34 ` bergner at gcc dot gnu.org
2023-06-21 23:19 ` segher at gcc dot gnu.org
2023-06-22 13:49 ` dje 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-101002-4-su7dXpMQ7l@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).