public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH][AArch64] Add optimized memchr
Date: Fri, 04 Nov 2016 09:01:00 -0000	[thread overview]
Message-ID: <CAFqB+PxrUX21K8kTvaggWhryA2wFnZJkMFbpjr6P=-TpEeRgbg@mail.gmail.com> (raw)
In-Reply-To: <AM5PR0802MB2610C243CC77E695AEE086DF83A00@AM5PR0802MB2610.eurprd08.prod.outlook.com>

On 2 November 2016 at 16:45, Wilco Dijkstra <Wilco.Dijkstra@arm.com> wrote:
>
> ping
>
> -----Original Message-----
> From: Wilco Dijkstra [mailto:wdijkstr@arm.com]
> Sent: 25 September 2015 14:21
> To: 'GNU C Library'
> Subject: [PATCH][AArch64] Add optimized memchr
>
> An optimized memchr was missing for AArch64. This version is similar to strchr and is significantly faster than the C version. Passes GLIBC tests.
>
> OK for commit?
>
> ChangeLog:
> 2015-09-25  Wilco Dijkstra  <wdijkstr@arm.com>
> 2015-09-25  Kevin Petit  <kevin.petit@arm.com>
>
>         * sysdeps/aarch64/memchr.S (__memchr): New file.
>

OK /Marcus

  reply	other threads:[~2016-11-04  9:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 16:41 Wilco Dijkstra
2016-04-15 12:42 ` Wilco Dijkstra
2016-05-12 14:02 ` Fw: " Wilco Dijkstra
2016-06-03 12:41   ` Wilco Dijkstra
2016-06-21 13:35     ` Wilco Dijkstra
2016-10-19 14:58 ` Wilco Dijkstra
2016-10-25 17:08   ` Adhemerval Zanella
2016-11-02 16:45   ` Wilco Dijkstra
2016-11-04  9:01     ` Marcus Shawcroft [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-09-25 13:21 Wilco Dijkstra
2015-09-26  8:46 ` Ondřej Bílka
2015-09-28  9:23   ` Wilco Dijkstra

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='CAFqB+PxrUX21K8kTvaggWhryA2wFnZJkMFbpjr6P=-TpEeRgbg@mail.gmail.com' \
    --to=marcus.shawcroft@gmail.com \
    --cc=Wilco.Dijkstra@arm.com \
    --cc=libc-alpha@sourceware.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).