public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Wed, 17 Jun 2020 15:27:37 +0000	[thread overview]
Message-ID: <bug-88398-4-A71lsLjHLl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #47 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> ---
memcmp is using wider reading in glibc; strncmp does not use wider reading.
memcmp is using "void *" as arguments, while strncmp is "char *".

  parent reply	other threads:[~2020-06-17 15:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-88398-4@http.gcc.gnu.org/bugzilla/>
2020-05-19  9:39 ` guojiufu at gcc dot gnu.org
2020-05-21  5:29 ` guojiufu at gcc dot gnu.org
2020-05-27  9:32 ` guojiufu at gcc dot gnu.org
2020-05-27  9:45 ` guojiufu at gcc dot gnu.org
2020-05-27 11:21 ` wilco at gcc dot gnu.org
2020-05-27 13:06 ` guojiufu at gcc dot gnu.org
2020-05-27 13:25 ` wilco at gcc dot gnu.org
2020-05-28  2:18 ` guojiufu at gcc dot gnu.org
2020-05-28  2:30 ` guojiufu at gcc dot gnu.org
2020-05-28 12:44 ` wilco at gcc dot gnu.org
2020-05-31 20:31 ` wschmidt at linux dot ibm.com
2020-06-02  2:49 ` guojiufu at gcc dot gnu.org
2020-06-02  6:35 ` rguenther at suse dot de
2020-06-04 14:15 ` guojiufu at gcc dot gnu.org
2020-06-08  2:45 ` guojiufu at gcc dot gnu.org
2020-06-08  9:22 ` wilco at gcc dot gnu.org
2020-06-09  3:46 ` guojiufu at gcc dot gnu.org
2020-06-09  3:49 ` guojiufu at gcc dot gnu.org
2020-06-10  9:56 ` guojiufu at gcc dot gnu.org
2020-06-10 10:03 ` wilco at gcc dot gnu.org
2020-06-12  4:20 ` guojiufu at gcc dot gnu.org
2020-06-12  4:47 ` guojiufu at gcc dot gnu.org
2020-06-17 15:27 ` guojiufu at gcc dot gnu.org [this message]
2021-05-04 12:32 ` rguenth at gcc dot gnu.org
2022-03-14 12:23 ` d_vampile at 163 dot com
2022-03-15 17:22 ` wilco 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-88398-4-A71lsLjHLl@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).