public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@adacore.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
	Mike Stump <mikestump@comcast.net>,
	David Edelsohn <dje.gcc@gmail.com>, Kewen Lin <linkw@gcc.gnu.org>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] ppc: testsuite: pr79004 needs -mlong-double-128
Date: Sun, 28 Apr 2024 05:20:55 -0300	[thread overview]
Message-ID: <or5xw1hp94.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <6f1df02a-c133-6297-b785-b05d135ca165@linux.ibm.com> (Kewen Lin's message of "Tue, 23 Apr 2024 16:55:15 +0800")

On Apr 23, 2024, "Kewen.Lin" <linkw@linux.ibm.com> wrote:

> This patch seemed to miss to CC gcc-patches list. :)

Oops, sorry, thanks for catching that.

Here it is.  FTR, you've already responded suggesting an apparent
preference for addressing PR105359, but since I meant to contribute it,
I'm reposting is to gcc-patches, now with a reference to the PR.


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.
---
 gcc/testsuite/gcc.target/powerpc/pr79004.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.target/powerpc/pr79004.c b/gcc/testsuite/gcc.target/powerpc/pr79004.c
index e411702dc98a9..061a0e83fe2ad 100644
--- a/gcc/testsuite/gcc.target/powerpc/pr79004.c
+++ b/gcc/testsuite/gcc.target/powerpc/pr79004.c
@@ -1,6 +1,6 @@
 /* { dg-do compile { target { powerpc*-*-* && lp64 } } } */
 /* { dg-require-effective-target powerpc_p9vector_ok } */
-/* { dg-options "-mdejagnu-cpu=power9 -O2 -mfloat128" } */
+/* { dg-options "-mdejagnu-cpu=power9 -O2 -mfloat128 -mlong-double-128" } */
 /* { dg-prune-output ".-mfloat128. option may not be fully supported" } */
 
 #include <math.h>


-- 
Alexandre Oliva, happy hacker            https://FSFLA.org/blogs/lxo/
   Free Software Activist                   GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive

  parent reply	other threads:[~2024-04-28  8:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02 16:52 enable __ieee128 for p9vector tests Alexandre Oliva
2021-04-12 21:04 ` Segher Boessenkool
2021-04-17  9:19   ` Alexandre Oliva
2022-04-13 23:37     ` Alexandre Oliva
2022-04-13 23:58       ` ppc: testsuite: bfp: enable float128 for __ieee128 Alexandre Oliva
2022-04-14 16:12         ` Segher Boessenkool
2022-04-13 23:58       ` ppc: testsuite: prune float128 partial support warnings Alexandre Oliva
2022-04-14 15:40         ` [PATCH] ppc: testsuite: pr79004 needs -mlong-double-128 (was: Re: ppc: testsuite: prune float128 partial support warnings) Alexandre Oliva
2022-04-23 13:33           ` [PATCH] ppc: testsuite: float128-hw{,4}.c need -mlong-double-128 (was: [PATCH] ppc: testsuite: pr79004 needs -mlong-double-128) Alexandre Oliva
2022-04-26 13:06             ` [PATCH] ppc: testsuite: float128-hw{, 4}.c " Segher Boessenkool
2022-04-26 16:49               ` [PATCH] ppc: testsuite: float128-hw{,4}.c need -mlong-double-128 Alexandre Oliva
     [not found]           ` <or5xw9oi60.fsf@lxoliva.fsfla.org>
     [not found]             ` <6f1df02a-c133-6297-b785-b05d135ca165@linux.ibm.com>
2024-04-28  8:20               ` Alexandre Oliva [this message]
2024-04-28  9:34                 ` [PATCH] ppc: testsuite: pr79004 needs -mlong-double-128 Kewen.Lin
2024-04-29  6:34                   ` Alexandre Oliva
2024-04-29  7:20                   ` Alexandre Oliva
2024-04-29  8:59                     ` Kewen.Lin
2024-04-29 23:11                       ` Alexandre Oliva
2024-05-08  8:36                         ` Kewen.Lin
2024-05-21  3:04                           ` [PATCH v2] [testsuite] xfail pr79004 on longdouble64; drop long_double_64bit (was: ppc: testsuite: pr79004 needs -mlong-double-128) Alexandre Oliva
2024-05-22  3:31                             ` Kewen.Lin
2022-04-14  0:00       ` [PATCH] ppc: testsuite: enable _Float128 type Alexandre Oliva
2022-04-14 16:06       ` enable __ieee128 for p9vector tests Segher Boessenkool
2022-04-14 16:02     ` Segher Boessenkool
2022-04-14 16:56       ` Alexandre Oliva
2022-04-14 17:11         ` Segher Boessenkool
2022-04-14 18:42           ` Alexandre Oliva
2022-04-14 22:41       ` [PATCH] ppc: testsuite: p9-vec-length: add -mno-strict-align and -misel (was: Re: enable __ieee128 for p9vector tests) 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=or5xw1hp94.fsf@lxoliva.fsfla.org \
    --to=oliva@adacore.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linkw@gcc.gnu.org \
    --cc=linkw@linux.ibm.com \
    --cc=mikestump@comcast.net \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    --cc=segher@kernel.crashing.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).