public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103605] [PowerPC] fmin/fmax should be inlined always with xsmindp/xsmaxdp
Date: Tue, 25 Jul 2023 02:43:10 +0000	[thread overview]
Message-ID: <bug-103605-4-XXdieT0m6s@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103605-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103605

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by HaoChen Gui <guihaoc@gcc.gnu.org>:

https://gcc.gnu.org/g:54ce3cbd285d453b954c281bb3ad38bee2f65330

commit r14-2758-g54ce3cbd285d453b954c281bb3ad38bee2f65330
Author: Haochen Gui <guihaoc@gcc.gnu.org>
Date:   Tue Jul 25 10:40:37 2023 +0800

    rs6000: Implemented f[min/max]_optab by xs[min/max]dp

    gcc/
            PR target/103605
            * config/rs6000/rs6000-builtin.cc (rs6000_gimple_fold_builtin):
Gimple
            fold RS6000_BIF_XSMINDP and RS6000_BIF_XSMAXDP when fast-math is
set.
            * config/rs6000/rs6000.md (FMINMAX): New int iterator.
            (minmax_op): New int attribute.
            (UNSPEC_FMAX, UNSPEC_FMIN): New unspecs.
            (f<minmax_op><mode>3): New pattern by UNSPEC_FMAX and UNSPEC_FMIN.
            * config/rs6000/rs6000-builtins.def (__builtin_vsx_xsmaxdp): Set
            pattern to fmaxdf3.
            (__builtin_vsx_xsmindp): Set pattern to fmindf3.

    gcc/testsuite/
            PR target/103605
            * gcc.target/powerpc/pr103605.h: New.
            * gcc.target/powerpc/pr103605-1.c: New.
            * gcc.target/powerpc/pr103605-2.c: New.

  parent reply	other threads:[~2023-07-25  2:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 16:21 [Bug target/103605] New: " pc at gcc dot gnu.org
2021-12-07 16:21 ` [Bug target/103605] " pc at gcc dot gnu.org
2022-04-26  9:27 ` guihaoc at gcc dot gnu.org
2022-04-26 18:35 ` pc at gcc dot gnu.org
2022-04-26 18:46 ` joseph at codesourcery dot com
2022-04-26 20:45 ` pc at gcc dot gnu.org
2022-04-27  5:32 ` guihaoc at gcc dot gnu.org
2022-04-28  3:22 ` linkw at gcc dot gnu.org
2022-05-10 12:21 ` segher at gcc dot gnu.org
2023-07-25  2:43 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-17  5:26 ` guihaoc at gcc dot gnu.org

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=bug-103605-4-XXdieT0m6s@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).