public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gmail.com>
To: Steve Ellcey <sellcey@mips.com>
Cc: libc-ports@sourceware.org
Subject: Re: [Patch, mips] Faster strcmp for mips
Date: Thu, 19 Feb 2015 07:25:00 -0000	[thread overview]
Message-ID: <CAEdQ38G5-2M2gPBthuzA3Ut27cvYUOy57nNE9H9SJ-1biO9+7A@mail.gmail.com> (raw)
In-Reply-To: <1384464221.2484.86.camel@ubuntu-sellcey>

On Thu, Nov 14, 2013 at 1:23 PM, Steve Ellcey <sellcey@mips.com> wrote:
>
> I have created an optimized strcmp routine for MIPS and would like to check
> it in.  I verified it by running 'make check' and I also ran 'make bench'
> to check the performance.  This function is slightly slower then the current
> generic strcmp for strings that are not aligned, but much faster when strings
> are aligned because it will then load and compare either 2, 4, or 8 bytes at a
> time.
>
> This means it could be loading bytes beyond the end of the strings being
> compared but it looks like other architecture specific strcmp functions
> are also doing this optimization and the newlib version of strcmp also does
> this.
>
> OK to checkin?
>
> I have attached the original and new bench-strcmp.out files in case anyone
> wants to compare the old and new strcmp performance results.
>
> Steve Ellcey
> sellcey@mips.com
>
>
> 2013-11-14  Steve Ellcey  <sellcey@mips.com>
>
>         * sysdeps/mips/strcmp.c: New.
>
>

Doesn't seem that this was ever committed?

  parent reply	other threads:[~2015-02-19  7:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 21:25 Steve Ellcey
2013-11-14 23:14 ` Ondřej Bílka
2013-11-15 18:21   ` Steve Ellcey
2013-11-15 19:02     ` Ondřej Bílka
2013-11-18 23:50       ` Steve Ellcey
2013-11-19  2:32         ` Ondřej Bílka
2013-11-15 18:48 ` Carlos O'Donell
2013-11-15 18:53   ` Steve Ellcey
2013-11-15 18:59     ` Carlos O'Donell
2015-02-19  7:25 ` Matt Turner [this message]
2015-02-19 18:12   ` Steve Ellcey

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=CAEdQ38G5-2M2gPBthuzA3Ut27cvYUOy57nNE9H9SJ-1biO9+7A@mail.gmail.com \
    --to=mattst88@gmail.com \
    --cc=libc-ports@sourceware.org \
    --cc=sellcey@mips.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).