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)] ppc: testsuite: pr79004 needs -mlong-double-128 Date: Sun, 21 Apr 2024 20:28:01 +0000 (GMT) [thread overview] Message-ID: <20240421202801.5C94A3858D39@sourceware.org> (raw) https://gcc.gnu.org/g:fe3c0a30e72c978dcd9a70d131b2e9cb9f90e8e0 commit fe3c0a30e72c978dcd9a70d131b2e9cb9f90e8e0 Author: Alexandre Oliva <oliva@adacore.com> Date: Sun Apr 21 17:24:28 2024 -0300 ppc: testsuite: pr79004 needs -mlong-double-128 Some of the asm opcodes expected by pr79004 depend on -mlong-double-128 to be output. E.g., without this flag, the conditions of patterns @extenddf<mode>2 and extendsf<mode>2 do not hold, and so GCC resorts to libcalls instead of even trying rs6000_expand_float128_convert. Perhaps the conditions are too strict, and they could enable the use of conversion insns involving __ieee128/_Float128 even with 64-bit long doubles. Alas, for now, we need this flag for the test to pass on target variants that use 64-bit long doubles. for gcc/testsuite/ChangeLog * gcc.target/powerpr/pr79004.c: Add -mlong-double-128. Diff: --- gcc/testsuite/gcc.target/powerpc/pr79004.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/testsuite/gcc.target/powerpc/pr79004.c b/gcc/testsuite/gcc.target/powerpc/pr79004.c index caf1f6c1eef..83f20ca2243 100644 --- a/gcc/testsuite/gcc.target/powerpc/pr79004.c +++ b/gcc/testsuite/gcc.target/powerpc/pr79004.c @@ -1,6 +1,7 @@ /* { dg-do compile { target { powerpc*-*-* && lp64 } } } */ /* { dg-require-effective-target powerpc_vsx_ok } */ /* { dg-options "-mdejagnu-cpu=power9 -mvsx -O2 -mfloat128" } */ +/* { dg-additional-options "-mlong-double-128" } */ #include <math.h>
next reply other threads:[~2024-04-21 20:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-21 20:28 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-04-28 5:22 Alexandre Oliva 2024-04-22 6:57 Alexandre Oliva 2024-04-22 5:13 Alexandre Oliva 2023-04-06 6:34 Alexandre Oliva 2023-03-30 14:07 Alexandre Oliva 2023-03-24 6:24 Alexandre Oliva 2023-03-23 3:47 Alexandre Oliva 2023-03-16 14:22 Alexandre Oliva 2023-03-15 14:05 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=20240421202801.5C94A3858D39@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).