public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: GNU C Library <libc-alpha@sourceware.org>,
	"Pandey, Sunil K" <sunil.k.pandey@intel.com>,
	 "Cornea, Marius" <marius.cornea@intel.com>,
	Florian Weimer <fweimer@redhat.com>
Subject: x86-64 assembly codes vs C source codes
Date: Tue, 21 Dec 2021 08:18:25 -0800	[thread overview]
Message-ID: <CAMe9rOovxq7b2wvXuPDt-2WF_yhuZ4=Pv8mf1yBZTSHRNqMG6w@mail.gmail.com> (raw)

Hi,

There are 421 x86-64 assembly source files.  Majority of
them have generic versions in C.  We added many x86-64
assembly source files for performance.   Most of x86-64
assembly source files started from the generic version in C.
They were compiled into assembly and optimized by hand.
Intel is committed to support x86-64 assembly source files
to improve performance and fix any bugs.

For 2.35, we'd like to add more x86-64 assembly source
files to libmvec.   The x86-64 assembly source files are the
preferred form for performance and accuracy today.

We will evaluate the generic alternative in the future
if it has similar performance and accuracy as the
assembly version, like:

ba4b8fab20 x86-64: Remove s_sincosf-sse2.S
4ca945e9c5 x86-64: Remove sysdeps/x86_64/fpu/s_cosf.S
9574c7b68d x86-64: Remove sysdeps/x86_64/fpu/s_sinf.S
e1f59bebd8 x86-64: Replace assembly versions of e_expf with generic e_expf.c
8537e0f6cf x86-64: Implement libmathvec IFUNC selectors in C
10a87ca476 x86-64: Implement libm IFUNC selectors in C
11ffcacb64 x86-64: Implement strcmp family IFUNC selectors in C
70fe2eb794 x86-64: Implement strcspn/strpbrk/strspn IFUNC selectors in C
9f4254b8bd x86-64: Implement wcscpy IFUNC selector in C
9ed0aa15d3 x86-64: Implement strcat family IFUNC selectors in C
b91a52d0d7 x86-64: Implement memcmp family IFUNC selectors in C
93e46f8773 x86-64: Implement memset family IFUNC selectors in C
5c3e322d3b x86-64: Implement memmove family IFUNC selectors in C
5a103908c0 x86-64: Implement strcpy family IFUNC selectors in C

Thanks.

-- 
H.J.

             reply	other threads:[~2021-12-21 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 16:18 H.J. Lu [this message]
2021-12-22 12:49 ` Adhemerval Zanella
2021-12-22 13:39   ` H.J. Lu
2021-12-22 14:23     ` Szabolcs Nagy
2021-12-22 15:36       ` H.J. Lu

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='CAMe9rOovxq7b2wvXuPDt-2WF_yhuZ4=Pv8mf1yBZTSHRNqMG6w@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=marius.cornea@intel.com \
    --cc=sunil.k.pandey@intel.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).