public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: bmahi496@linux.ibm.com
To: libc-alpha@sourceware.org
Cc: rajis@linux.ibm.com, MAHESH BODAPATI <bmahi496@linux.ibm.com>
Subject: [PATCH 0/2] *** Add optimized memchr for power10 ***
Date: Mon, 13 Nov 2023 10:33:57 -0600	[thread overview]
Message-ID: <20231113163359.1468671-1-bmahi496@linux.ibm.com> (raw)

From: MAHESH BODAPATI <bmahi496@linux.ibm.com>

*** Series of 2 patches which are having the memchr implementation and benchmark
results ***

MAHESH BODAPATI (2):
  powerpc : Add optimized memchr for POWER10
  powerpc: memchr benchmarking results with power10 optimized memchr.

 memchr_bench_report.txt                       | 1130 +++++++++++++++++
 sysdeps/powerpc/powerpc64/le/power10/memchr.S |  315 +++++
 sysdeps/powerpc/powerpc64/multiarch/Makefile  |    9 +-
 .../powerpc64/multiarch/ifunc-impl-list.c     |    6 +
 .../powerpc64/multiarch/memchr-power10.S      |   28 +
 sysdeps/powerpc/powerpc64/multiarch/memchr.c  |   20 +-
 6 files changed, 1498 insertions(+), 10 deletions(-)
 create mode 100644 memchr_bench_report.txt
 create mode 100644 sysdeps/powerpc/powerpc64/le/power10/memchr.S
 create mode 100644 sysdeps/powerpc/powerpc64/multiarch/memchr-power10.S

-- 
2.39.3


             reply	other threads:[~2023-11-13 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 16:33 bmahi496 [this message]
2023-11-13 16:33 ` [PATCH 1/2] powerpc : Add optimized memchr for POWER10 bmahi496
2023-11-13 16:33 ` [PATCH 2/2] powerpc: memchr benchmarking results with power10 optimized memchr bmahi496
     [not found] <20231113162939.1265581-1-bmahi496@linux.ibm.com>
2023-11-13 17:02 ` [PATCH 0/2] *** Add optimized memchr for power10 *** MAHESH BODAPATI

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=20231113163359.1468671-1-bmahi496@linux.ibm.com \
    --to=bmahi496@linux.ibm.com \
    --cc=libc-alpha@sourceware.org \
    --cc=rajis@linux.ibm.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).