From: Ulrich Drepper <drepper@cygnus.com>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: Andreas Jaeger <aj@arthur.rhein-neckar.de>,
egcs@cygnus.com, GNU C Library <libc-linux@gnu.org>
Subject: Re: A patch for libm-ieee754
Date: Sun, 22 Feb 1998 13:33:00 -0000 [thread overview]
Message-ID: <r2wwen1g8k.fsf@happy.cygnus.com> (raw)
In-Reply-To: <9802221954.AA00210@moene.indiv.nluug.nl>
Toon Moene <toon@moene.indiv.nluug.nl> writes:
> Andreas, would it be useful to mobilise some people to help do the
> math related stuff in glibc-2.x ?
>
> I might be able to stirr some interest in the group that did
> `enquire.c' originally (CWI - het Centrum voor Wiskunde en
> Informatica in Amsterdam).
Actually I think that for glibc 2.1 we should just fix the bugs which
were located. For one it is too late now to make major changes in
libm and second, for glibc 2.2 or 2.3 we need to think about a new
organization for the libm since we have to support long double not
only on ix86 and m68k but also on the new architectures which use
different formats (128 bit).
We would like to see tests for the libm precision any time and I would
appreciate if somebody could activate people with the necessary
knowledge.
-- Uli
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
next prev parent reply other threads:[~1998-02-22 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199802220053.TAA29191@rabi.phys.columbia.edu>
1998-02-21 17:50 ` Who is fixing libm-ieee754? H.J. Lu
1998-02-21 18:55 ` A patch for libm-ieee754 H.J. Lu
1998-02-22 7:42 ` Andreas Jaeger
1998-02-22 13:03 ` Toon Moene
1998-02-22 13:33 ` Ulrich Drepper [this message]
1998-02-22 13:42 ` Andreas Jaeger
1998-02-22 18:18 ` Geoffrey KEATING
1998-02-22 18:39 ` David Edelsohn
1998-02-22 19:30 ` Geoffrey KEATING
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=r2wwen1g8k.fsf@happy.cygnus.com \
--to=drepper@cygnus.com \
--cc=aj@arthur.rhein-neckar.de \
--cc=egcs@cygnus.com \
--cc=libc-linux@gnu.org \
--cc=toon@moene.indiv.nluug.nl \
/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).