public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] [PR99708] [rs6000] don't expect __ibm128 with 64-bit long double Date: Fri, 24 Mar 2023 06:25:57 +0000 (GMT) [thread overview] Message-ID: <20230324062557.E4D5238768B8@sourceware.org> (raw) https://gcc.gnu.org/g:ee8e94a50ea4af309cd26bd7fcda2848e52e2cc4 commit ee8e94a50ea4af309cd26bd7fcda2848e52e2cc4 Author: Alexandre Oliva <oliva@adacore.com> Date: Fri Mar 24 02:57:17 2023 -0300 [PR99708] [rs6000] don't expect __ibm128 with 64-bit long double When long double is 64-bit wide, as on vxworks, the rs6000 backend defines neither the __ibm128 type nor the __SIZEOF_IBM128__ macro, but pr99708.c expected both to be always defined. Adjust the test to match the implementation. for gcc/testsuite/ChangeLog * gcc.target/powerpc/pr99708.c: Accept lack of __SIZEOF_IBM128__ when long double is 64-bit wide. Diff: --- gcc/testsuite/gcc.target/powerpc/pr99708.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.target/powerpc/pr99708.c b/gcc/testsuite/gcc.target/powerpc/pr99708.c index 02b40ebc40d..fca6296d9c8 100644 --- a/gcc/testsuite/gcc.target/powerpc/pr99708.c +++ b/gcc/testsuite/gcc.target/powerpc/pr99708.c @@ -14,7 +14,13 @@ int main (void) { if (__SIZEOF_FLOAT128__ != sizeof (__float128) - || __SIZEOF_IBM128__ != sizeof (__ibm128)) +#ifdef __SIZEOF_IBM128__ /* Not defined, and no __ibm128 type on targets whose + long double is 64-bit. */ + || __SIZEOF_IBM128__ != sizeof (__ibm128) +#else + || __SIZEOF_LONG_DOUBLE__ * __CHAR_BIT__ != 64 +#endif + ) abort (); return 0;
next reply other threads:[~2023-03-24 6:25 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-24 6:25 Alexandre Oliva [this message] 2023-03-25 14:53 Alexandre Oliva 2023-03-30 14:08 Alexandre Oliva 2023-04-06 6:35 Alexandre Oliva 2023-04-06 7:35 Alexandre Oliva 2023-04-07 3:36 Alexandre Oliva
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=20230324062557.E4D5238768B8@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-cvs@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).