From: Segher Boessenkool <segher@kernel.crashing.org>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org,
Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Mike Stump <mikestump@comcast.net>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: ppc: testsuite: bfp: enable float128 for __ieee128
Date: Thu, 14 Apr 2022 11:12:43 -0500 [thread overview]
Message-ID: <20220414161243.GK614@gate.crashing.org> (raw)
In-Reply-To: <orlew8tu1x.fsf_-_@lxoliva.fsfla.org>
On Wed, Apr 13, 2022 at 08:58:18PM -0300, Alexandre Oliva wrote:
>
> Multiple bfp tests expect -mcpu=power[89] to enable the __ieee128
> type, but on targets that #define TARGET_FLOAT128_ENABLE_TYPE 0, that
> is not the case. Since they are compile-time tests and effective
> target support for powerpc_p9vector_ok is required, adding -mfloat128
> is safe. This patch does so, and arranges for the warning raised on
> such systems to be pruned.
>
> Tested on x86_64-linux-gnu x ppc64-vx7r2 with gcc-11. Ok to install?
Not okay. We rely everywhere else on -mcpu=power9 (etc.) to enable VSX
just as well.
You should not change such defaults for your platform.
Segher
next prev parent reply other threads:[~2022-04-14 16:15 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 [this message]
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 ` [PATCH] ppc: testsuite: pr79004 needs -mlong-double-128 Alexandre Oliva
2024-04-28 9:34 ` 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=20220414161243.GK614@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=oliva@adacore.com \
--cc=ro@cebitec.uni-bielefeld.de \
/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).