public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/28358] New: f64xdivf128 and f64xmulf128 spurious underflows
Date: Mon, 20 Sep 2021 22:34:52 +0000	[thread overview]
Message-ID: <bug-28358-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28358
           Summary: f64xdivf128 and f64xmulf128 spurious underflows
           Product: glibc
           Version: 2.34
            Status: NEW
          Severity: normal
          Priority: P2
         Component: math
          Assignee: unassigned at sourceware dot org
          Reporter: jsm28 at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-* i?86-* ia64-*

The round-to-odd computations used in the libm functions that round their
results to a narrower format can yield spurious underflow exceptions in the
following circumstances: the narrowing only narrows the precision of the type
and not the exponent range (i.e., it's narrowing _Float128 to _Float64x on
x86_64, x86 or ia64), the architecture does after-rounding tininess detection
(which applies to all those architectures), the result is inexact, tiny before
rounding but not tiny after rounding (with the chosen rounding mode) for
_Float64x (which is possible for narrowing mul, div and fma, not for narrowing
add, sub or sqrt), so the underflow exception resulting from the toward-zero
computation in _Float128 is spurious for _Float64x.  For example, this applies
to the following test inputs if added to auto-libm-test-in:

div 0x1p-16382 0x1.00000000000000001p0
mul 0x0.ffffffffffffffff8p-16382 0x1.00000000000000001p0

I'm working on a fix for this issue, which showed up while working on
implementing the narrowing fma functions.

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

             reply	other threads:[~2021-09-20 22:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 22:34 jsm28 at gcc dot gnu.org [this message]
2021-09-21 21:55 ` [Bug math/28358] " cvs-commit at gcc dot gnu.org
2021-09-21 21:57 ` jsm28 at gcc dot gnu.org

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-28358-131@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).