public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "goldstein.w.n at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/28354] For x86_64 string/memory functions use of EVEX registers sets HI16_ZMM_state adding context switch overhead
Date: Mon, 20 Sep 2021 02:28:55 +0000	[thread overview]
Message-ID: <bug-28354-131-P8Jm15Jvse@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28354-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28354

Noah Goldstein <goldstein.w.n at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |goldstein.w.n at gmail dot com
             Target|                            |x86_64-linux

--- Comment #1 from Noah Goldstein <goldstein.w.n at gmail dot com> ---
My general opinion is that we should move the current evex function to evex-rtm
and add a new class of evex function which may use avx512 functions but stay in
the ymm0-ymm15 register range.

Benefits:

1) evex instructions cost more code size (+2 bytes at least)
2) Its impossible to encode certain useful instructions with the evex prefix
(i.e `vpcmpeq`)
3) We may be adding 1024 bytes to uses context switches.


Costs:

1) vzeroupper is not free (in terms of code size or execution).
2) more total code size consumer by the library (this is limited by the fact
that they will be in their own section and users will generally only stay in
one section for all string/memory functions)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2021-09-20  2:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20  2:23 [Bug string/28354] New: " goldstein.w.n at gmail dot com
2021-09-20  2:28 ` goldstein.w.n at gmail dot com [this message]
2021-09-20 14:09 ` [Bug string/28354] " hjl.tools at gmail dot com
2021-09-22 21:10 ` goldstein.w.n at gmail dot com

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=bug-28354-131-P8Jm15Jvse@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).