From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: "libc-ports@sourceware.org" <libc-ports@sourceware.org>
Subject: Re: [COMMITTED] hppa: Update libm-test-ulps.
Date: Wed, 15 May 2013 20:22:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1305152018350.21321@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5193B7DD.4090600@redhat.com>
It's not *new* here, but ulps for ceil, floor, rint, round, trunc indicate
you've got bugs in those functions for long double; they shouldn't have
any ulps at all. And the ulps for llrint, llround also shouldn't be
there, and include negative values, which should never happen even when
the functions are buggy.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-05-15 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 16:29 Carlos O'Donell
2013-05-15 20:22 ` Joseph S. Myers [this message]
2013-05-15 21:00 ` Joseph S. Myers
2013-05-15 21:12 ` Carlos O'Donell
2013-05-15 21:16 ` Joseph S. Myers
2013-05-15 21:08 ` [COMMITTED] hppa: Cleanup libm-test-ulps Carlos O'Donell
2013-07-24 3:34 [COMMITTED] hppa: Update libm-test-ulps Carlos O'Donell
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=Pine.LNX.4.64.1305152018350.21321@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=libc-ports@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).