public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/115086] New: bic is not used when the non-not part is a constant
Date: Tue, 14 May 2024 09:45:01 +0000	[thread overview]
Message-ID: <bug-115086-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 115086
           Summary: bic is not used when the non-not part is a constant
           Product: gcc
           Version: 15.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---
            Target: aarch64

Take:
```
int g2(int a,int c)
{
  int b = 4 & ~c;
  return b;
}
```

Currently GCC produces:
```
g2:
        mvn     w0, w1
        and     w0, w0, 4
        ret
```
But producing bic is better for most (if not all) modern cores due to the
instruction that generates the constant would be "free". That is GCC should
produce:
```
g2:
        mov     w8, 4
        bic     w0, w8, w1
        ret
```

Which is what clang/LLVM produces.

             reply	other threads:[~2024-05-14  9:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14  9:45 pinskia at gcc dot gnu.org [this message]
2024-05-14  9:49 ` [Bug target/115086] " pinskia at gcc dot gnu.org
2024-05-14  9:50 ` rearnsha at gcc dot gnu.org
2024-05-15  5:11 ` pinskia at gcc dot gnu.org
2024-05-15  7:38 ` pinskia at gcc dot gnu.org
2024-05-15 10:37 ` pinskia 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-115086-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).