From: Bill Schmidt <wschmidt@linux.ibm.com>
To: gcc-patches@gcc.gnu.org
Cc: dje.gcc@gmail.com, segher@kernel.crashing.org
Subject: Re: [PATCH 7/8] rs6000: vec_neg built-ins wrongly require POWER8
Date: Mon, 7 Feb 2022 09:48:24 -0600 [thread overview]
Message-ID: <76110a86-82e1-84af-0168-bf0c766487ac@linux.ibm.com> (raw)
In-Reply-To: <16a48501c2e15d0a781ead8b44ca912dae90d717.1643390744.git.wschmidt@linux.ibm.com>
Hi Segher,
Thanks for all the reviews for this series! I'd like to gently ping the last two patches.
BR,
Bill
On 1/28/22 11:50 AM, Bill Schmidt via Gcc-patches wrote:
> As the subject states. Fixing this is accomplished by moving the built-ins
> to the correct stanzas, [altivec] and [vsx].
>
> Bootstrapped and tested on powerpc64le-linux-gnu with no regressions.
> Is this okay for trunk?
>
> Thanks,
> Bill
>
>
> 2022-01-27 Bill Schmidt <wschmidt@linux.ibm.com>
>
> gcc/
> * config/rs6000/rs6000-builtin.def (NEG_V16QI): Move to [altivec]
> stanza.
> (NEG_V4SF): Likewise.
> (NEG_V4SI): Likewise.
> (NEG_V8HI): Likewise.
> (NEG_V2DF): Move to [vsx] stanza.
> (NEG_V2DI): Likewise.
> ---
> gcc/config/rs6000/rs6000-builtins.def | 36 +++++++++++++--------------
> 1 file changed, 18 insertions(+), 18 deletions(-)
>
> diff --git a/gcc/config/rs6000/rs6000-builtins.def b/gcc/config/rs6000/rs6000-builtins.def
> index 2bb997a5279..c8f0cf332eb 100644
> --- a/gcc/config/rs6000/rs6000-builtins.def
> +++ b/gcc/config/rs6000/rs6000-builtins.def
> @@ -410,6 +410,18 @@
> const vss __builtin_altivec_nabs_v8hi (vss);
> NABS_V8HI nabsv8hi2 {}
>
> + const vsc __builtin_altivec_neg_v16qi (vsc);
> + NEG_V16QI negv16qi2 {}
> +
> + const vf __builtin_altivec_neg_v4sf (vf);
> + NEG_V4SF negv4sf2 {}
> +
> + const vsi __builtin_altivec_neg_v4si (vsi);
> + NEG_V4SI negv4si2 {}
> +
> + const vss __builtin_altivec_neg_v8hi (vss);
> + NEG_V8HI negv8hi2 {}
> +
> void __builtin_altivec_stvebx (vsc, signed long, void *);
> STVEBX altivec_stvebx {stvec}
>
> @@ -1175,6 +1187,12 @@
> const vsll __builtin_altivec_nabs_v2di (vsll);
> NABS_V2DI nabsv2di2 {}
>
> + const vd __builtin_altivec_neg_v2df (vd);
> + NEG_V2DF negv2df2 {}
> +
> + const vsll __builtin_altivec_neg_v2di (vsll);
> + NEG_V2DI negv2di2 {}
> +
> void __builtin_altivec_stvx_v2df (vd, signed long, void *);
> STVX_V2DF altivec_stvx_v2df {stvec}
>
> @@ -2118,24 +2136,6 @@
> const vus __builtin_altivec_nand_v8hi_uns (vus, vus);
> NAND_V8HI_UNS nandv8hi3 {}
>
> - const vsc __builtin_altivec_neg_v16qi (vsc);
> - NEG_V16QI negv16qi2 {}
> -
> - const vd __builtin_altivec_neg_v2df (vd);
> - NEG_V2DF negv2df2 {}
> -
> - const vsll __builtin_altivec_neg_v2di (vsll);
> - NEG_V2DI negv2di2 {}
> -
> - const vf __builtin_altivec_neg_v4sf (vf);
> - NEG_V4SF negv4sf2 {}
> -
> - const vsi __builtin_altivec_neg_v4si (vsi);
> - NEG_V4SI negv4si2 {}
> -
> - const vss __builtin_altivec_neg_v8hi (vss);
> - NEG_V8HI negv8hi2 {}
> -
> const vsc __builtin_altivec_orc_v16qi (vsc, vsc);
> ORC_V16QI orcv16qi3 {}
>
next prev parent reply other threads:[~2022-02-07 15:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 17:50 [PATCH 0/8] rs6000: Built-in function cleanups and bug fixes Bill Schmidt
2022-01-28 17:50 ` [PATCH 1/8] rs6000: More factoring of overload processing Bill Schmidt
2022-01-28 19:11 ` Segher Boessenkool
2022-01-28 21:19 ` Bill Schmidt
2022-01-28 23:09 ` Segher Boessenkool
2022-02-01 14:49 ` [PATCH v2 " Bill Schmidt
2022-02-01 21:48 ` Segher Boessenkool
2022-02-02 18:46 ` Bill Schmidt
2022-02-03 14:44 ` [PATCH v3 " Bill Schmidt
2022-02-04 1:24 ` Segher Boessenkool
2022-01-28 17:50 ` [PATCH 2/8] rs6000: Don't #ifdef "short" built-in names Bill Schmidt
2022-01-28 20:32 ` Segher Boessenkool
2022-01-28 21:21 ` Bill Schmidt
2022-01-28 17:50 ` [PATCH 3/8] rs6000: Convert <x> built-in constraints to <x,y> form Bill Schmidt
2022-01-28 23:24 ` [PATCH 3/8] rs6000: Convert <x> built-in constraints to <x, y> form Segher Boessenkool
2022-01-31 17:21 ` [PATCH 3/8] rs6000: Convert <x> built-in constraints to <x,y> form Bill Schmidt
2022-01-31 17:28 ` [PATCH 3/8] rs6000: Convert <x> built-in constraints to <x, y> form Segher Boessenkool
2022-01-31 17:31 ` [PATCH 3/8] rs6000: Convert <x> built-in constraints to <x,y> form Bill Schmidt
2022-02-01 14:53 ` [PATCH v2 3/8] rs6000: Unify error messages for built-in constant restrictions Bill Schmidt
2022-02-01 22:16 ` Segher Boessenkool
2022-01-28 17:50 ` [PATCH 4/8] rs6000: Consolidate target built-ins code Bill Schmidt
2022-01-31 21:32 ` Segher Boessenkool
2022-01-31 22:01 ` Bill Schmidt
2022-01-31 22:33 ` Segher Boessenkool
2022-01-28 17:50 ` [PATCH 5/8] rs6000: Fix LE code gen for vec_cnt[lt]z_lsbb [PR95082] Bill Schmidt
2022-02-01 23:01 ` Segher Boessenkool
2022-01-28 17:50 ` [PATCH 6/8] rs6000: Remove -m[no-]fold-gimple flag [PR103686] Bill Schmidt
2022-02-02 23:21 ` Segher Boessenkool
2022-01-28 17:50 ` [PATCH 7/8] rs6000: vec_neg built-ins wrongly require POWER8 Bill Schmidt
2022-02-07 15:48 ` Bill Schmidt [this message]
2022-03-30 18:04 ` Segher Boessenkool
2022-01-28 17:50 ` [PATCH 8/8] rs6000: Fix some missing built-in attributes [PR104004] Bill Schmidt
2022-03-15 13:18 ` rs6000 patch ping: " Jakub Jelinek
2022-03-30 12:28 ` rs6000 patch ping^2: " Jakub Jelinek
2022-03-30 23:07 ` rs6000 patch ping: " Segher Boessenkool
2022-03-31 22:17 ` Segher Boessenkool
2022-03-30 17:41 ` will schmidt
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=76110a86-82e1-84af-0168-bf0c766487ac@linux.ibm.com \
--to=wschmidt@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).