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/106562] PRU: Inefficient code for zero check of 64-bit (boolean) AND result
Date: Wed, 30 Aug 2023 19:05:58 +0000	[thread overview]
Message-ID: <bug-106562-4-M4TyJmpBR8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106562-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Dimitar Dimitrov <dimitar@gcc.gnu.org>:

https://gcc.gnu.org/g:ee077d0c5793e1d4ad8d3b033ef2f0225ba6bd59

commit r14-3578-gee077d0c5793e1d4ad8d3b033ef2f0225ba6bd59
Author: Dimitar Dimitrov <dimitar@dinux.eu>
Date:   Tue Jun 13 22:20:13 2023 +0300

    pru: Add cstore expansion patterns

    Add cstore patterns for the two specific operations which can be
    efficiently expanded using the UMIN instruction:
      X != 0
      X == 0
    The rest of the operations are rejected, and left to be expanded
    by the common expansion code.

            PR target/106562

    gcc/ChangeLog:

            * config/pru/predicates.md (const_0_operand): New predicate.
            (pru_cstore_comparison_operator): Ditto.
            * config/pru/pru.md (cstore<mode>4): New pattern.
            (cstoredi4): Ditto.

    gcc/testsuite/ChangeLog:

            * gcc.target/pru/pr106562-10.c: New test.
            * gcc.target/pru/pr106562-11.c: New test.
            * gcc.target/pru/pr106562-5.c: New test.
            * gcc.target/pru/pr106562-6.c: New test.
            * gcc.target/pru/pr106562-7.c: New test.
            * gcc.target/pru/pr106562-8.c: New test.
            * gcc.target/pru/pr106562-9.c: New test.

    Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>

  parent reply	other threads:[~2023-08-30 19:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 19:41 [Bug target/106562] New: PRU: Inefficient code for zero check of 64-bit " dimitar at gcc dot gnu.org
2022-08-08 19:42 ` [Bug target/106562] " dimitar at gcc dot gnu.org
2022-09-18 18:04 ` [Bug target/106562] PRU: Inefficient code for zero check of 64-bit (boolean) " dimitar at gcc dot gnu.org
2022-10-05 18:11 ` dimitar at gcc dot gnu.org
2022-10-09 11:39 ` cvs-commit at gcc dot gnu.org
2023-06-07 19:02 ` dimitar at gcc dot gnu.org
2023-06-07 19:26 ` pinskia at gcc dot gnu.org
2023-08-29 19:38 ` dimitar at gcc dot gnu.org
2023-08-30 19:05 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-30 20:13 ` dimitar 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-106562-4-M4TyJmpBR8@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).