Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: dave.anglin@nrc-cnrc.gc.ca, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] fenv laid to rest, 50% done porting dbl-64 to ldbl-64, no testing yet.
Date: Mon, 20 Oct 2003 15:04:30 -0400	[thread overview]
Message-ID: <20031020190430.GF32666@systemhalted> (raw)
In-Reply-To: <200310201749.h9KHnHQ3001830@hiauly1.hia.nrc.ca>

On Mon, Oct 20, 2003 at 01:49:17PM -0400, John David Anglin wrote:
> > Yes, I have already taken this into account. Thanks for all the help
> > with spec interpretation. I appreciate the feedback. We pass all the
> > fenv tests in glibc, but still fail the long double support. I'm about
> > 50% done porting dbl-64 to ldbl-64, might get done in the next few 
> > weeks. It would finally give us a functioning long double :)
> 
> I think we should hold off on implementing this until we get a final
> decision from HP on whether they will release their quadlib or not.

Noted. I have reordered my hacking queue.

a- Generate new testing deb's for glibc
	= Includes providing debian with a new .dpatch
	(1-2 days)
b- Fix _r_debug.r_map loader problems.
	(Timeline unknown)
c- Finish light-weight kernel syscalls for atomic ops
	(A few weeks)
d- Continue implementing ldbl-64 based on dbl-64.
	= The first 50% was a "test the waters" patch.
	= It looks *very* feasible and easy to test.
	= Function renaming, rewriting, casting, and mangling.
	(A few weeks)

In parallel with my usual upstream pushes.

If HP gets up off their haunches before I get to "d-" then they win :),
else I will continue my work on ldbl-64. I *will* hold-off on the
release of such an implementation in favour of the 128-bit ldbl. I know
full well that once we release the ldbl-64 it will become our ABI.

c.

  reply	other threads:[~2003-10-20 19:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-19 21:51 [parisc-linux] HPPA FPU Specification? (FE_INEXACT raised by accident) Carlos O'Donell
2003-10-19 23:16 ` [parisc-linux] " John David Anglin
2003-10-20  5:02   ` Carlos O'Donell
2003-10-20 15:30     ` John David Anglin
2003-10-20 16:01       ` Carlos O'Donell
2003-10-20 16:31         ` John David Anglin
2003-10-20 16:56           ` John David Anglin
2003-10-20 17:34             ` [parisc-linux] fenv laid to rest, 50% done porting dbl-64 to ldbl-64, no testing yet Carlos O'Donell
2003-10-20 17:49               ` John David Anglin
2003-10-20 19:04                 ` Carlos O'Donell [this message]
2003-10-21 10:42                 ` Joel Soete
2003-10-21 17:31                   ` John David Anglin
2003-10-20 17:31           ` [parisc-linux] Re: HPPA FPU Specification? (FE_INEXACT raised by accident) 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=20031020190430.GF32666@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@lists.parisc-linux.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