public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dimitar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106562] New: PRU: Inefficient code for zero check of 64-bit AND result
Date: Mon, 08 Aug 2022 19:41:42 +0000	[thread overview]
Message-ID: <bug-106562-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106562
           Summary: PRU: Inefficient code for zero check of 64-bit AND
                    result
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dimitar at gcc dot gnu.org
  Target Milestone: ---

GCC generates inefficient code for the following C snippet:

char test(uint64_t a, uint64_t b)
{
        return a && b;
}

test:
        or      r0.b0, r14.b0, r14.b1
        or      r0.b0, r0.b0, r14.b2
        or      r0.b0, r0.b0, r14.b3
        or      r0.b0, r0.b0, r15.b0
        or      r0.b0, r0.b0, r15.b1
        or      r0.b0, r0.b0, r15.b2
        or      r0.b0, r0.b0, r15.b3
        qbeq    .L4, r0.b0, 0
        mov     r14, r16
        mov     r15, r17
        sub     r2, r2, 2
        rsb     r0, r16, 0
        rsc     r1, r17, 0
        mov     r17, r14
        mov     r18, r15
        sbbo    r3.b2, r2, 0, 2
        ldi     r16.b0, (63) & 0xffff
        or      r14, r0, r17
        or      r15, r1, r18
        call    %label(__pruabi_lsrll)
        lbbo    r3.b2, r2, 0, 2
        add     r2, r2, 2
        ret

             reply	other threads:[~2022-08-08 19:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 19:41 dimitar at gcc dot gnu.org [this message]
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
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@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).