public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc(refs/users/aoliva/heads/testme)] ppc: testsuite: float128-hw{, 4}.c need -mlong-double-128
@ 2023-03-15 14:05 Alexandre Oliva
0 siblings, 0 replies; 6+ messages in thread
From: Alexandre Oliva @ 2023-03-15 14:05 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:f7a651b1426e26456e18249be9c986bb622c780e
commit f7a651b1426e26456e18249be9c986bb622c780e
Author: Alexandre Oliva <oliva@adacore.com>
Date: Sat Apr 23 10:30:02 2022 -0300
ppc: testsuite: float128-hw{,4}.c need -mlong-double-128
Just like pr79004, float128-hw.c requires -mlong-double-128 for some
the expected asm opcodes to be output on target variants that have
64-bit long doubles. That's because their expanders,
e.g. floatsi<mode>2 for FLOAT128 modes, are conditioned on
TARGET_LONG_DOUBLE_128, which is not set on target variants that use
64-bit long double.
float128-hw4.c doesn't even compile without -mlong-double-128, on
64-bit long double target variants. The error is "invalid parameter
combination for AltiVec intrinsic" in get_float128_exponent,
get_float128_mantissa, and set_float128_exponent_float128, presumably
caused by rs6000_builtin_type_compatible's refusal to consider
_Float128 compatible when TARGET_LONG_DOUBLE_128 is not set.
Since these are compile tests, -mlong-double-128 doesn't hurt even on
target variants that use 64-bit long double, and enables both tests to
pass.
for gcc/testsuite/ChangeLog
* gcc.target/powerpc/float128-hw.c: Add -mlong-double-128.
* gcc.target/powerpc/float128-hw4.c: Likewise.
Diff:
---
gcc/testsuite/gcc.target/powerpc/float128-hw.c | 1 +
gcc/testsuite/gcc.target/powerpc/float128-hw4.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw.c b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
index 8c9beafa90a..c2be7ee6ead 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2" } */
+/* { dg-additional-options "-mlong-double-128" } */
#ifndef TYPE
#define TYPE _Float128
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
index fc149169bc6..dd5f932fb1a 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2 -mabi=ieeelongdouble -Wno-psabi" } */
+/* { dg-additional-options "-mlong-double-128" } */
/* Insure that the ISA 3.0 IEEE 128-bit floating point built-in functions can
be used with long double when the default is IEEE 128-bit. */
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gcc(refs/users/aoliva/heads/testme)] ppc: testsuite: float128-hw{, 4}.c need -mlong-double-128
@ 2023-04-06 6:34 Alexandre Oliva
0 siblings, 0 replies; 6+ messages in thread
From: Alexandre Oliva @ 2023-04-06 6:34 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:8eca9315a684c4e35d8dce513f9afa60db30ff62
commit 8eca9315a684c4e35d8dce513f9afa60db30ff62
Author: Alexandre Oliva <oliva@adacore.com>
Date: Wed Apr 5 11:26:57 2023 -0300
ppc: testsuite: float128-hw{,4}.c need -mlong-double-128
Just like pr79004, float128-hw.c requires -mlong-double-128 for some
the expected asm opcodes to be output on target variants that have
64-bit long doubles. That's because their expanders,
e.g. floatsi<mode>2 for FLOAT128 modes, are conditioned on
TARGET_LONG_DOUBLE_128, which is not set on target variants that use
64-bit long double.
float128-hw4.c doesn't even compile without -mlong-double-128, on
64-bit long double target variants. The error is "invalid parameter
combination for AltiVec intrinsic" in get_float128_exponent,
get_float128_mantissa, and set_float128_exponent_float128, presumably
caused by rs6000_builtin_type_compatible's refusal to consider
_Float128 compatible when TARGET_LONG_DOUBLE_128 is not set.
Since these are compile tests, -mlong-double-128 doesn't hurt even on
target variants that use 64-bit long double, and enables both tests to
pass.
for gcc/testsuite/ChangeLog
* gcc.target/powerpc/float128-hw.c: Add -mlong-double-128.
* gcc.target/powerpc/float128-hw4.c: Likewise.
Diff:
---
gcc/testsuite/gcc.target/powerpc/float128-hw.c | 1 +
gcc/testsuite/gcc.target/powerpc/float128-hw4.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw.c b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
index 8c9beafa90a..c2be7ee6ead 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2" } */
+/* { dg-additional-options "-mlong-double-128" } */
#ifndef TYPE
#define TYPE _Float128
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
index fc149169bc6..dd5f932fb1a 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2 -mabi=ieeelongdouble -Wno-psabi" } */
+/* { dg-additional-options "-mlong-double-128" } */
/* Insure that the ISA 3.0 IEEE 128-bit floating point built-in functions can
be used with long double when the default is IEEE 128-bit. */
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gcc(refs/users/aoliva/heads/testme)] ppc: testsuite: float128-hw{, 4}.c need -mlong-double-128
@ 2023-03-30 14:07 Alexandre Oliva
0 siblings, 0 replies; 6+ messages in thread
From: Alexandre Oliva @ 2023-03-30 14:07 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:07d4898e49720ad54a835fe2e3f12afc50d355fe
commit 07d4898e49720ad54a835fe2e3f12afc50d355fe
Author: Alexandre Oliva <oliva@adacore.com>
Date: Thu Mar 30 05:07:03 2023 -0300
ppc: testsuite: float128-hw{,4}.c need -mlong-double-128
Just like pr79004, float128-hw.c requires -mlong-double-128 for some
the expected asm opcodes to be output on target variants that have
64-bit long doubles. That's because their expanders,
e.g. floatsi<mode>2 for FLOAT128 modes, are conditioned on
TARGET_LONG_DOUBLE_128, which is not set on target variants that use
64-bit long double.
float128-hw4.c doesn't even compile without -mlong-double-128, on
64-bit long double target variants. The error is "invalid parameter
combination for AltiVec intrinsic" in get_float128_exponent,
get_float128_mantissa, and set_float128_exponent_float128, presumably
caused by rs6000_builtin_type_compatible's refusal to consider
_Float128 compatible when TARGET_LONG_DOUBLE_128 is not set.
Since these are compile tests, -mlong-double-128 doesn't hurt even on
target variants that use 64-bit long double, and enables both tests to
pass.
for gcc/testsuite/ChangeLog
* gcc.target/powerpc/float128-hw.c: Add -mlong-double-128.
* gcc.target/powerpc/float128-hw4.c: Likewise.
Diff:
---
gcc/testsuite/gcc.target/powerpc/float128-hw.c | 1 +
gcc/testsuite/gcc.target/powerpc/float128-hw4.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw.c b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
index 8c9beafa90a..c2be7ee6ead 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2" } */
+/* { dg-additional-options "-mlong-double-128" } */
#ifndef TYPE
#define TYPE _Float128
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
index fc149169bc6..dd5f932fb1a 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2 -mabi=ieeelongdouble -Wno-psabi" } */
+/* { dg-additional-options "-mlong-double-128" } */
/* Insure that the ISA 3.0 IEEE 128-bit floating point built-in functions can
be used with long double when the default is IEEE 128-bit. */
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gcc(refs/users/aoliva/heads/testme)] ppc: testsuite: float128-hw{, 4}.c need -mlong-double-128
@ 2023-03-24 6:25 Alexandre Oliva
0 siblings, 0 replies; 6+ messages in thread
From: Alexandre Oliva @ 2023-03-24 6:25 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:cd754a356f96f6aa2779a0e685e509a7cde649ac
commit cd754a356f96f6aa2779a0e685e509a7cde649ac
Author: Alexandre Oliva <oliva@adacore.com>
Date: Thu Mar 23 00:44:41 2023 -0300
ppc: testsuite: float128-hw{,4}.c need -mlong-double-128
Just like pr79004, float128-hw.c requires -mlong-double-128 for some
the expected asm opcodes to be output on target variants that have
64-bit long doubles. That's because their expanders,
e.g. floatsi<mode>2 for FLOAT128 modes, are conditioned on
TARGET_LONG_DOUBLE_128, which is not set on target variants that use
64-bit long double.
float128-hw4.c doesn't even compile without -mlong-double-128, on
64-bit long double target variants. The error is "invalid parameter
combination for AltiVec intrinsic" in get_float128_exponent,
get_float128_mantissa, and set_float128_exponent_float128, presumably
caused by rs6000_builtin_type_compatible's refusal to consider
_Float128 compatible when TARGET_LONG_DOUBLE_128 is not set.
Since these are compile tests, -mlong-double-128 doesn't hurt even on
target variants that use 64-bit long double, and enables both tests to
pass.
for gcc/testsuite/ChangeLog
* gcc.target/powerpc/float128-hw.c: Add -mlong-double-128.
* gcc.target/powerpc/float128-hw4.c: Likewise.
Diff:
---
gcc/testsuite/gcc.target/powerpc/float128-hw.c | 1 +
gcc/testsuite/gcc.target/powerpc/float128-hw4.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw.c b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
index 8c9beafa90a..c2be7ee6ead 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2" } */
+/* { dg-additional-options "-mlong-double-128" } */
#ifndef TYPE
#define TYPE _Float128
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
index fc149169bc6..dd5f932fb1a 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2 -mabi=ieeelongdouble -Wno-psabi" } */
+/* { dg-additional-options "-mlong-double-128" } */
/* Insure that the ISA 3.0 IEEE 128-bit floating point built-in functions can
be used with long double when the default is IEEE 128-bit. */
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gcc(refs/users/aoliva/heads/testme)] ppc: testsuite: float128-hw{, 4}.c need -mlong-double-128
@ 2023-03-23 3:47 Alexandre Oliva
0 siblings, 0 replies; 6+ messages in thread
From: Alexandre Oliva @ 2023-03-23 3:47 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:e087d4daaef174a845774e7d98dcb27b50db042b
commit e087d4daaef174a845774e7d98dcb27b50db042b
Author: Alexandre Oliva <oliva@adacore.com>
Date: Thu Mar 23 00:44:41 2023 -0300
ppc: testsuite: float128-hw{,4}.c need -mlong-double-128
Just like pr79004, float128-hw.c requires -mlong-double-128 for some
the expected asm opcodes to be output on target variants that have
64-bit long doubles. That's because their expanders,
e.g. floatsi<mode>2 for FLOAT128 modes, are conditioned on
TARGET_LONG_DOUBLE_128, which is not set on target variants that use
64-bit long double.
float128-hw4.c doesn't even compile without -mlong-double-128, on
64-bit long double target variants. The error is "invalid parameter
combination for AltiVec intrinsic" in get_float128_exponent,
get_float128_mantissa, and set_float128_exponent_float128, presumably
caused by rs6000_builtin_type_compatible's refusal to consider
_Float128 compatible when TARGET_LONG_DOUBLE_128 is not set.
Since these are compile tests, -mlong-double-128 doesn't hurt even on
target variants that use 64-bit long double, and enables both tests to
pass.
for gcc/testsuite/ChangeLog
* gcc.target/powerpc/float128-hw.c: Add -mlong-double-128.
* gcc.target/powerpc/float128-hw4.c: Likewise.
Diff:
---
gcc/testsuite/gcc.target/powerpc/float128-hw.c | 1 +
gcc/testsuite/gcc.target/powerpc/float128-hw4.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw.c b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
index 8c9beafa90a..c2be7ee6ead 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2" } */
+/* { dg-additional-options "-mlong-double-128" } */
#ifndef TYPE
#define TYPE _Float128
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
index fc149169bc6..dd5f932fb1a 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2 -mabi=ieeelongdouble -Wno-psabi" } */
+/* { dg-additional-options "-mlong-double-128" } */
/* Insure that the ISA 3.0 IEEE 128-bit floating point built-in functions can
be used with long double when the default is IEEE 128-bit. */
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gcc(refs/users/aoliva/heads/testme)] ppc: testsuite: float128-hw{, 4}.c need -mlong-double-128
@ 2023-03-16 14:22 Alexandre Oliva
0 siblings, 0 replies; 6+ messages in thread
From: Alexandre Oliva @ 2023-03-16 14:22 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:48052388dd78bd92c1dfe78a0a6d2c264d220cf0
commit 48052388dd78bd92c1dfe78a0a6d2c264d220cf0
Author: Alexandre Oliva <oliva@adacore.com>
Date: Sat Apr 23 10:30:02 2022 -0300
ppc: testsuite: float128-hw{,4}.c need -mlong-double-128
Just like pr79004, float128-hw.c requires -mlong-double-128 for some
the expected asm opcodes to be output on target variants that have
64-bit long doubles. That's because their expanders,
e.g. floatsi<mode>2 for FLOAT128 modes, are conditioned on
TARGET_LONG_DOUBLE_128, which is not set on target variants that use
64-bit long double.
float128-hw4.c doesn't even compile without -mlong-double-128, on
64-bit long double target variants. The error is "invalid parameter
combination for AltiVec intrinsic" in get_float128_exponent,
get_float128_mantissa, and set_float128_exponent_float128, presumably
caused by rs6000_builtin_type_compatible's refusal to consider
_Float128 compatible when TARGET_LONG_DOUBLE_128 is not set.
Since these are compile tests, -mlong-double-128 doesn't hurt even on
target variants that use 64-bit long double, and enables both tests to
pass.
for gcc/testsuite/ChangeLog
* gcc.target/powerpc/float128-hw.c: Add -mlong-double-128.
* gcc.target/powerpc/float128-hw4.c: Likewise.
Diff:
---
gcc/testsuite/gcc.target/powerpc/float128-hw.c | 1 +
gcc/testsuite/gcc.target/powerpc/float128-hw4.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw.c b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
index 8c9beafa90a..c2be7ee6ead 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2" } */
+/* { dg-additional-options "-mlong-double-128" } */
#ifndef TYPE
#define TYPE _Float128
diff --git a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
index fc149169bc6..dd5f932fb1a 100644
--- a/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
+++ b/gcc/testsuite/gcc.target/powerpc/float128-hw4.c
@@ -2,6 +2,7 @@
/* { dg-require-effective-target powerpc_p9vector_ok } */
/* { dg-require-effective-target float128 } */
/* { dg-options "-mpower9-vector -O2 -mabi=ieeelongdouble -Wno-psabi" } */
+/* { dg-additional-options "-mlong-double-128" } */
/* Insure that the ISA 3.0 IEEE 128-bit floating point built-in functions can
be used with long double when the default is IEEE 128-bit. */
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-04-06 6:34 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-15 14:05 [gcc(refs/users/aoliva/heads/testme)] ppc: testsuite: float128-hw{, 4}.c need -mlong-double-128 Alexandre Oliva
2023-03-16 14:22 Alexandre Oliva
2023-03-23 3:47 Alexandre Oliva
2023-03-24 6:25 Alexandre Oliva
2023-03-30 14:07 Alexandre Oliva
2023-04-06 6:34 Alexandre Oliva
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).