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/108338] use mtvsrws for lowpart DI->SF conversion on P9
Date: Sat, 07 Oct 2023 07:57:47 +0000	[thread overview]
Message-ID: <bug-108338-4-zCEpi6asY4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108338-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jiu Fu Guo <guojiufu@gcc.gnu.org>:

https://gcc.gnu.org/g:5f56b76ff1c15118200204569389f85cca4e32d3

commit r14-4444-g5f56b76ff1c15118200204569389f85cca4e32d3
Author: Jiufu Guo <guojiufu@linux.ibm.com>
Date:   Thu Sep 28 17:00:04 2023 +0800

    rs6000: optimize moving to sf from highpart di

    Currently, we have the pattern "movsf_from_si2" which was trying
    to support moving high part DI to SF.

    But current pattern only accepts "ashiftrt":
    XX:SF=bitcast:SF(subreg(YY:DI>>32),0), but actually "lshiftrt" should
    also be ok.
    And current pattern only supports BE.

    Here, updating the pattern to support BE and "lshiftrt".

            PR target/108338

    gcc/ChangeLog:

            * config/rs6000/predicates.md (lowpart_subreg_operator): New
            define_predicate.
            * config/rs6000/rs6000.md (any_rshift): New code_iterator.
            (movsf_from_si2): Rename to ...
            (movsf_from_si2_<code>): ... this.

    gcc/testsuite/ChangeLog:

            * gcc.target/powerpc/pr108338.c: New test.

  reply	other threads:[~2023-10-07  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09  6:35 [Bug target/108338] New: " guojiufu at gcc dot gnu.org
2023-10-07  7:57 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-07  7:57 ` [Bug target/108338] " cvs-commit at gcc dot gnu.org
2023-10-07  8:03 ` guojiufu 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-108338-4-zCEpi6asY4@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).