public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/15536] ulp (0x0.0p0) is not FP_SUBNORMAL!
Date: Mon, 03 Jun 2013 20:23:00 -0000	[thread overview]
Message-ID: <bug-15536-131-sjWgkZFrUE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15536-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15536

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
Resolved.

commit 8b0ccb2d7fd1ec646a622a16bd64e356739ffca3
Author: Carlos O'Donell <carlos@redhat.com>
Date:   Mon Jun 3 14:49:48 2013 -0400

    BZ #15536: Fix ulp for 128-bit IBM long double.

    In 128-bit IBM long double the precision of the type
    decreases as you approach subnormal numbers, equaling
    that of a double for subnormal numbers. Therefore
    adjust the computation in ulp to use 2^(MIN_EXP - MANT_DIG)
    which is correct for FP_SUBNORMAL for all types.

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


  parent reply	other threads:[~2013-06-03 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-26  9:29 [Bug math/15536] New: " schwab@linux-m68k.org
2013-05-26  9:30 ` [Bug math/15536] " schwab@linux-m68k.org
2013-05-27 17:31 ` carlos at redhat dot com
2013-05-31  5:39 ` carlos at redhat dot com
2013-05-31 19:28 ` joseph at codesourcery dot com
2013-06-03 20:23 ` carlos at redhat dot com [this message]
2014-06-13 17:36 ` fweimer at redhat 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-15536-131-sjWgkZFrUE@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).