public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/27461] Unixbench/whetstone-double performance regression on glibc2.32
Date: Wed, 24 Feb 2021 05:36:07 +0000	[thread overview]
Message-ID: <bug-27461-131-CiABlpFrvC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27461-131@http.sourceware.org/bugzilla/>

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

Siddhesh Poyarekar <siddhesh at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |siddhesh at sourceware dot org

--- Comment #1 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
ISTM that the core assumption when we merged _finite with regular functions was
that the overhead of error checking was negligible, but that's clearly not true
for the whetstone benchmark.

It would be interesting to see what's different between the whetstone workload
and the ones we have in the glibc microbenchmark and find a way to harmonize
them.

FWIW, we had noticed rounding mode changing overheads were most noticeable in a
UnixBench benchmark (can't remember which one but it led to [1]) too compared
to others, so it's likely that the workloads there are heavy on inputs that
need more error/mode processing.


[1] commit 2506109403de69bd454de27835d42e6eb6ec3abc
Author: Siddhesh Poyarekar <siddhesh@redhat.com>
Date:   Wed Jun 12 10:36:48 2013 +0530

    Set/restore rounding mode only when needed

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

  parent reply	other threads:[~2021-02-24  5:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  4:57 [Bug math/27461] New: " xuchunmei at linux dot alibaba.com
2021-02-24  4:58 ` [Bug math/27461] " xuchunmei at linux dot alibaba.com
2021-02-24  4:59 ` xuchunmei at linux dot alibaba.com
2021-02-24  5:36 ` siddhesh at sourceware dot org [this message]
2021-02-24  9:45 ` nsz at gcc dot gnu.org
2021-02-24 10:49 ` wdijkstr at arm dot com
2021-02-25 11:04 ` xuchunmei at linux dot alibaba.com
2021-03-01 12:06 ` xuchunmei at linux dot alibaba.com
2021-03-02  4:59 ` xuchunmei at linux dot alibaba.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-27461-131-CiABlpFrvC@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).