This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: Which failures to fix first?
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Roland McGrath" <roland at redhat dot com>
- Cc: libc-ports at sources dot redhat dot com
- Date: Sun, 11 Jun 2006 13:51:05 -0400
- Subject: Re: Which failures to fix first?
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=jgLVH4UxVJ2vEb8xuaACZN1IcfGodFUW4dQGQ4FKYObZzH1poP1jMADPXvJCaxtMhSAnGsS/NjXLZeNz0LgnhIAy+QgZeDU6Qzl15lcK8+SyP2UTjkDit4+SuH2SU43XSF0SjXSgd/rgwrsIceBHxh6uwn8HjWeUuB9A3sanFm4=
- References: <119aab440606090759h7d552324gd8d6b663ecf41df0@mail.gmail.com> <20060609195344.DBD3D180072@magilla.sf.frob.com>
On 6/9/06, Roland McGrath <roland@redhat.com> wrote:
I'd do the stdio-common problems first (that seems random). Then the elf/
failures. The linuxthreads and rt failures might well be kernel problems,
and whether kernel or linuxthreads port bugs they are often hard to figure out.
Perhaps another orthogonal question might help answer some issues I'm examining.
No HP PARISC processor implements long double 128-bit in hardware. All
of the implementations require software libraries, which will not be
made public.
I have removed "ieee754/ldbl-128" from Implies. I believe the only
onther change is to create an hppa specific "wordsize.h" with "#define
__NO_LONG_DOUBLE_MATH" in order to move hppa into supporting 64-bit
long doubles. This has been coordinated with gcc, to change long
double to 64-bits.
Is there anything else I'm missing?
Cheers,
Carlos.