public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bschmidt@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>,
	       Nick Clifton <nickc@redhat.com>
Subject: Re: Thoughts on memcmp expansion (PR43052)
Date: Tue, 31 May 2016 15:05:00 -0000	[thread overview]
Message-ID: <574D9B25.7040302@redhat.com> (raw)
In-Reply-To: <55238d87-b52b-b743-5a5f-5afb43355b26@redhat.com>

On 05/30/2016 11:37 AM, Florian Weimer wrote:

>>  * Expand __memcmp_eq for small constant sizes with loads and
>>    comparison, fall back to a memcmp call.
>
> Should we export such a function from glibc?  I expect it's fairly
> common.  Computing the tail difference costs a few cycles.

At the moment the patch ensures that no actual memcmp_eq function is 
called, it's either expanded inline or we fall back to memcmp. But 
there's no reason why it couldn't be added under some appropriate name.


Bernd

      reply	other threads:[~2016-05-31 14:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 16:58 Bernd Schmidt
2016-01-18  9:22 ` Richard Biener
2016-04-28 18:36   ` Bernd Schmidt
2016-05-02 12:52     ` Richard Biener
2016-05-02 12:57       ` Bernd Schmidt
2016-05-02 13:14         ` Richard Biener
2016-05-12 17:14           ` Bernd Schmidt
2016-05-13 10:20             ` Richard Biener
2016-05-13 13:05               ` Bernd Schmidt
2016-05-13 13:07                 ` Richard Biener
2016-05-13 13:13                   ` Bernd Schmidt
2016-05-13 13:53                     ` Joseph Myers
2016-05-13 14:00                       ` Bernd Schmidt
2016-05-13 20:41                         ` Joseph Myers
2016-05-31 23:50                           ` Bernd Schmidt
2016-01-18 12:22 ` Nick Clifton
2016-01-19 21:36 ` Jeff Law
2016-05-30 11:29 ` Florian Weimer
2016-05-31 15:05   ` Bernd Schmidt [this message]

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=574D9B25.7040302@redhat.com \
    --to=bschmidt@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nickc@redhat.com \
    /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).