public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "denis.campredon at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/103647] New: constant array comparison not always folded
Date: Fri, 10 Dec 2021 11:01:22 +0000	[thread overview]
Message-ID: <bug-103647-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103647
           Summary: constant array comparison not always folded
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: denis.campredon at gmail dot com
  Target Milestone: ---

On trunk and gcc 11, with -O2 the following functions are not optimized to 
xor eax, eax

------------
bool f() {
    char a[] = {'a', 'c'};
    char b[] = {'a', 'b'};
    return __builtin_memcmp(a, b, 2);
}

bool g() {
    char a[] = {'a', 'b'};
    char b[] = {'a', 'b', 'c'};
    return __builtin_memcmp(a, b, 2);
}
------------

.LC1:
        .string "ab"
.LC0:
        .string "ac"
f():
        movzx   eax, WORD PTR .LC1[rip]
        cmp     WORD PTR .LC0[rip], ax
        setne   al
        ret
g():
        cmp     WORD PTR .LC1[rip], 25185
        setne   al
        ret

             reply	other threads:[~2021-12-10 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 11:01 denis.campredon at gmail dot com [this message]
2021-12-10 20:29 ` [Bug tree-optimization/103647] " pinskia at gcc dot gnu.org
2021-12-10 20:31 ` pinskia at gcc dot gnu.org
2022-01-04  9:24 ` rguenth 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-103647-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).