From: "Paul A. Clarke" <pc@us.ibm.com>
To: wschmidt@linux.ibm.com
Cc: gcc-patches@gcc.gnu.org, segher@kernel.crashing.org
Subject: Re: [PATCH v3 1/6] rs6000: Support SSE4.1 "round" intrinsics
Date: Mon, 30 Aug 2021 16:16:43 -0500 [thread overview]
Message-ID: <20210830211643.GB2032444@li-24c3614c-2adc-11b2-a85c-85f334518bdb.ibm.com> (raw)
In-Reply-To: <992ac7bc-85d5-62b9-fadc-5388e372979f@linux.ibm.com>
On Fri, Aug 27, 2021 at 08:44:43AM -0500, Bill Schmidt via Gcc-patches wrote:
> On 8/23/21 2:03 PM, Paul A. Clarke wrote:
> > + __fpscr_save.__fr = __builtin_mffsl ();
>
> As pointed out in the v1 review, __builtin_mffsl is enabled (or supposed to
> be) only for POWER9 and later. This will fail to work on POWER8 and earlier
> when the new builtins support is complete and this is enforced more
> carefully. Please #ifdef and use __builtin_mffs on earlier processors.
> Please do this everywhere this occurs.
>
> I think you got some contradictory guidance on this, but trust me, this will
> break.
The confusing thing is that _builtin_mffsl is explicitly supported on earlier
processors, if I read the code right (from gcc/config/rs6000/rs6000.md):
--
(define_expand "rs6000_mffsl"
[(set (match_operand:DF 0 "gpc_reg_operand")
(unspec_volatile:DF [(const_int 0)] UNSPECV_MFFSL))]
"TARGET_HARD_FLOAT"
{
/* If the low latency mffsl instruction (ISA 3.0) is available use it,
otherwise fall back to the older mffs instruction to emulate the mffsl
instruction. */
if (!TARGET_P9_MISC)
{
rtx tmp1 = gen_reg_rtx (DFmode);
/* The mffs instruction reads the entire FPSCR. Emulate the mffsl
instruction using the mffs instruction and masking the result. */
emit_insn (gen_rs6000_mffs (tmp1));
...
--
Is that going away? If so, that would be a possible (undesirable?)
API change, no?
PC
next prev parent reply other threads:[~2021-08-30 21:16 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 19:03 [PATCH v3 0/6] rs6000: Support more SSE4 intrinsics Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 1/6] rs6000: Support SSE4.1 "round" intrinsics Paul A. Clarke
2021-08-27 13:44 ` Bill Schmidt
2021-08-27 13:47 ` Bill Schmidt
2021-08-30 21:16 ` Paul A. Clarke [this message]
2021-08-30 21:24 ` Bill Schmidt
2021-10-07 23:08 ` Segher Boessenkool
2021-10-07 23:39 ` Segher Boessenkool
2021-10-08 1:04 ` Paul A. Clarke
2021-10-08 17:39 ` Segher Boessenkool
2021-10-08 19:27 ` Paul A. Clarke
2021-10-08 22:31 ` Segher Boessenkool
2021-10-11 13:46 ` Paul A. Clarke
2021-10-11 16:28 ` Segher Boessenkool
2021-10-11 17:31 ` Paul A. Clarke
2021-10-11 22:04 ` Segher Boessenkool
2021-10-12 19:35 ` Paul A. Clarke
2021-10-12 22:25 ` Segher Boessenkool
2021-10-19 0:36 ` Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 2/6] rs6000: Support SSE4.1 "min" and "max" intrinsics Paul A. Clarke
2021-08-27 13:47 ` Bill Schmidt
2021-10-11 19:28 ` Segher Boessenkool
2021-10-12 1:42 ` [COMMITTED v4 " Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 3/6] rs6000: Simplify some SSE4.1 "test" intrinsics Paul A. Clarke
2021-08-27 13:48 ` Bill Schmidt
2021-10-11 20:50 ` Segher Boessenkool
2021-10-12 1:47 ` [COMMITTED v4 " Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 4/6] rs6000: Support SSE4.1 "cvt" intrinsics Paul A. Clarke
2021-08-27 13:49 ` Bill Schmidt
2021-10-11 21:52 ` Segher Boessenkool
2021-10-12 1:51 ` [COMMITTED v4 " Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 5/6] rs6000: Support more SSE4 "cmp", "mul", "pack" intrinsics Paul A. Clarke
2021-08-27 15:21 ` Bill Schmidt
2021-08-27 18:52 ` Paul A. Clarke
2021-10-11 23:07 ` Segher Boessenkool
2021-10-12 1:55 ` [COMMITTED v4 " Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 6/6] rs6000: Guard some x86 intrinsics implementations Paul A. Clarke
2021-08-27 15:25 ` Bill Schmidt
2021-10-12 0:11 ` Segher Boessenkool
2021-10-13 17:04 ` Paul A. Clarke
2021-10-13 23:47 ` Segher Boessenkool
2021-10-19 0:26 ` Paul A. Clarke
2021-09-16 14:59 ` [PATCH v3 0/6] rs6000: Support more SSE4 intrinsics Paul A. Clarke
2021-10-04 18:26 ` Paul A. Clarke
2021-10-07 22:25 ` Segher Boessenkool
2021-10-08 0:29 ` Paul A. Clarke
2021-10-12 0:15 ` Segher Boessenkool
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=20210830211643.GB2032444@li-24c3614c-2adc-11b2-a85c-85f334518bdb.ibm.com \
--to=pc@us.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.com \
/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).