Ping [PATCH 1/2] Move xx* builtins to vsx.md.

2021-05-24 Thread Michael Meissner via Gcc-patches
the patch if this is rejected). | Date: Tue, 18 May 2021 16:46:47 -0400 | Subject: [PATCH 1/2] Move xx* builtins to vsx.md. | Message-ID: <20210518204647.ga16...@ibm-toto.the-meissners.org> -- Michael Meissner, IBM IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA email:

Re: [PATCH 1/2] Move xx* builtins to vsx.md.

2021-05-20 Thread Michael Meissner via Gcc-patches
On Thu, May 20, 2021 at 02:30:24PM -0500, will schmidt wrote: > > +;; XXPERMX built-in function support > > +(define_expand "xxpermx" > > + [(set (match_operand:V2DI 0 "register_operand" "+wa") > > + (unspec:V2DI [(match_operand:V2DI 1 "register_operand" "wa") > > +

Re: [PATCH 1/2] Move xx* builtins to vsx.md.

2021-05-20 Thread will schmidt via Gcc-patches
On Tue, 2021-05-18 at 16:46 -0400, Michael Meissner wrote: > [PATCH 1/2] Move xx* builtins to vsx.md. > Hi, > I noticed that the xx built-in functions (xxspltiw, xxspltidp, xxsplti32dx, > xxeval, xxblend, and xxpermx) were all defined in altivec.md. However, since > the XX i

[PATCH 1/2] Move xx* builtins to vsx.md.

2021-05-18 Thread Michael Meissner via Gcc-patches
[PATCH 1/2] Move xx* builtins to vsx.md. I noticed that the xx built-in functions (xxspltiw, xxspltidp, xxsplti32dx, xxeval, xxblend, and xxpermx) were all defined in altivec.md. However, since the XX instructions can take both traditional floating point and Altivec registers, these built