This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH], Enable fminf<x> and fmaxf<x>
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Michael Meissner <meissner at linux dot vnet dot ibm dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>, Segher Boessenkool <segher at kernel dot crashing dot org>, David Edelsohn <dje dot gcc at gmail dot com>, Bill Schmidt <wschmidt at linux dot vnet dot ibm dot com>
- Date: Mon, 13 Nov 2017 11:19:34 +0100
- Subject: Re: [PATCH], Enable fminf<x> and fmaxf<x>
- Authentication-results: sourceware.org; auth=none
- References: <20171109134441.GA17446@ibm-tiger.the-meissners.org>
On Thu, Nov 9, 2017 at 2:44 PM, Michael Meissner
<meissner@linux.vnet.ibm.com> wrote:
> In my previous patch enabling some of the built-in functions for _Float<N> and
> _Float<N>X datatypes, I missed making fminf128 and fmaxf128 generate the
> minimum and maximum inline code when -ffast-math is used. This patch to
> match.pd enables the code generation using if-then-else if the machine does not
> have an appropriate min/max instruction (the power9 hardware does not have
> min/max instructions for quad floating point).
>
> I have done builds on x86-64, little endian power8, and little endian power9
> prototype systems. All builds bootstrapped and had no regressions. Can I
> check this patch into the trunk?
Ok.
Richard.
> [gcc]
> 2017-11-09 Michael Meissner <meissner@linux.vnet.ibm.com>
>
> * match.pd: Convert fminf<N>, fminf<N>x, fmax<N>, and fmax<N>x
> into the min/max operations for _Float<N> and _Float<N>X types.
>
> [gcc/testsuite]
> 2017-11-09 Michael Meissner <meissner@linux.vnet.ibm.com>
>
> * gcc.target/powerpc/float128-minmax.c: New test.
>
> --
> Michael Meissner, IBM
> IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
> email: meissner@linux.vnet.ibm.com, phone: +1 (978) 899-4797