From: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>, Lili Cui <lili.cui@intel.com>
Cc: Shen-Ta Hsieh <ibmibmibm.tw@gmail.com>,
"H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v4 2/2] x86_64: roundeven with sse4.1 support
Date: Thu, 28 May 2020 05:31:57 -0700 [thread overview]
Message-ID: <CAMe9rOpqAir1CKK+R3m4ZCHSQpoXjvEdZcVPLtCHW8mcivBung@mail.gmail.com> (raw)
In-Reply-To: <877dwwckq2.fsf@oldenburg2.str.redhat.com>
On Thu, May 28, 2020 at 5:22 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * H. J. Lu via Libc-alpha:
>
> >> Here is a benchmark result on my AMD Ryzen 9 3900X system:
> >
> > Since we don't know or may not care SSE4 machines without AVX,
> > should we make it to AVX only?
>
> What about Goldmont/Tremont? Those are current CPUs which do not
> support AVX, but I think they have sufficient SSE4 support levels for
> this change.
>
Good point. Lili, please collect glibc micro benchmark roundeven/roundevenf
data before and after:
https://sourceware.org/pipermail/libc-alpha/2020-May/113533.html
on Tremont.
--
H.J.
next prev parent reply other threads:[~2020-05-28 12:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 17:23 [PATCH] Add benchtests for roundeven and roundevenf Shen-Ta Hsieh
2020-03-27 23:25 ` Joseph Myers
2020-05-02 15:02 ` [PATCH v4 1/2] math: redirect roundeven function Shen-Ta Hsieh via Libc-alpha
2020-05-02 15:02 ` [PATCH v4 2/2] x86_64: roundeven with sse4.1 support Shen-Ta Hsieh via Libc-alpha
2020-05-28 12:05 ` H.J. Lu via Libc-alpha
2020-05-28 12:22 ` Florian Weimer via Libc-alpha
2020-05-28 12:31 ` H.J. Lu via Libc-alpha [this message]
2020-05-29 8:48 ` Cui, Lili via Libc-alpha
2020-05-29 11:29 ` H.J. Lu via Libc-alpha
2020-06-01 1:28 ` Cui, Lili via Libc-alpha
2020-06-01 2:04 ` H.J. Lu via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMe9rOpqAir1CKK+R3m4ZCHSQpoXjvEdZcVPLtCHW8mcivBung@mail.gmail.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=ibmibmibm.tw@gmail.com \
--cc=lili.cui@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).