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/106769] PPCLE: vec_extract(vector unsigned int) unnecessary rldicl after mfvsrwz
Date: Mon, 09 Oct 2023 06:38:39 +0000	[thread overview]
Message-ID: <bug-106769-4-DXivS5KESy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106769-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 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:c1e474785859c9630fcae19c8d2d606f5642c636

commit r14-4485-gc1e474785859c9630fcae19c8d2d606f5642c636
Author: Haochen Gui <guihaoc@gcc.gnu.org>
Date:   Mon Oct 9 14:34:46 2023 +0800

    rs6000: support 32bit inline lrint

    gcc/
            PR target/88558
            * config/rs6000/rs6000.md (lrint<mode>di2): Remove TARGET_FPRND
            from insn condition.
            (lrint<mode>si2): New insn pattern for 32bit lrint.

    gcc/testsuite/
            PR target/106769
            * gcc.target/powerpc/pr88558.h: New.
            * gcc.target/powerpc/pr88558-p7.c: New.
            * gcc.target/powerpc/pr88558-p8.c: New.

      parent reply	other threads:[~2023-10-09  6:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29  6:57 [Bug target/106769] New: " jens.seifert at de dot ibm.com
2023-05-30  9:14 ` [Bug target/106769] " guihaoc at gcc dot gnu.org
2023-05-31  9:03 ` guihaoc at gcc dot gnu.org
2023-06-02 15:04 ` bergner at gcc dot gnu.org
2023-06-06  8:35 ` guihaoc at gcc dot gnu.org
2023-08-16  6:24 ` cvs-commit at gcc dot gnu.org
2023-08-17  5:27 ` guihaoc at gcc dot gnu.org
2023-10-09  6:38 ` cvs-commit at gcc dot gnu.org [this message]

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-106769-4-DXivS5KESy@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).