From: Matthew Wilcox <willy@debian.org>
To: Carlos O'Donell <carlos@baldric.uwo.ca>,
parisc-linux@lists.parisc-linux.org,
Randolph Chung <tausq@debian.org>, Jeff Bailey <jbailey@nisa.net>
Subject: Re: [parisc-linux] glibc 2.3.1 - It's alive! - patches
Date: Mon, 11 Nov 2002 01:21:29 +0000 [thread overview]
Message-ID: <20021111012129.A29998@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20021111010517.GA13575@systemhalted>; from carlos@baldric.uwo.ca on Sun, Nov 10, 2002 at 08:05:17PM -0500
On Sun, Nov 10, 2002 at 08:05:17PM -0500, Carlos O'Donell wrote:
> Lastly, I think that the fp* tests suffer from the printf bug?
Last I looked, we suffered from the fact that glibc thinks `long double'
is 96 bits, gcc thinks `long double' is 64 bits and gcc-hpux thinks that
`long double' is 128 bits. I've been whining about this for over a year
and nothing's happened. I think it's fairly clear that not much uses
long double, otherwise we'd've noticed more failure cases. So changing
both gcc & glibc to a 128-bit long double is the Right Thing to do and
we can just suck up this ABI breakage.
In case anyone's wondering, the architecture specifies 32-bit, 64-bit and
128-bit floating point registers as being available. My understanding is
that no processor has actually implemented the 128-bit floating point ops
(except maybe load and store) and they always trap to the FP emulation
code (which we copied from HPUX).
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-11-11 1:21 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 1:05 [parisc-linux] glibc 2.3.1 - It's alive! - patches Carlos O'Donell
2002-11-11 1:19 ` John David Anglin
2002-11-11 17:12 ` Carlos O'Donell
2002-11-11 17:36 ` John David Anglin
2002-11-11 18:00 ` Matthew Wilcox
2002-11-11 18:20 ` Carlos O'Donell
2002-11-11 18:58 ` Carlos O'Donell
2002-11-11 20:42 ` Carlos O'Donell
2002-11-11 20:57 ` John David Anglin
2002-11-11 21:17 ` Carlos O'Donell
2002-11-11 21:33 ` John David Anglin
2002-11-12 5:31 ` [parisc-linux] simple testcase for binutils visibility problem Randolph Chung
2002-11-12 5:58 ` John David Anglin
2002-11-11 21:16 ` [parisc-linux] glibc 2.3.1 - It's alive! - patches Carlos O'Donell
2002-11-11 22:36 ` John David Anglin
2002-11-11 22:44 ` Carlos O'Donell
2002-11-11 22:53 ` John David Anglin
2002-11-11 23:27 ` Carlos O'Donell
2002-11-12 0:22 ` John David Anglin
2002-11-12 1:23 ` Carlos O'Donell
2002-11-12 4:13 ` John David Anglin
2002-11-12 15:44 ` John David Anglin
2002-11-12 17:42 ` Jim Hull
2002-11-12 17:53 ` John David Anglin
2002-11-12 18:43 ` Jim Hull
2002-11-12 19:02 ` John David Anglin
2002-11-12 19:31 ` Jim Hull
2002-11-12 19:38 ` John David Anglin
2002-11-13 19:22 ` Carlos O'Donell
2002-11-13 20:16 ` John David Anglin
2002-11-17 21:54 ` John David Anglin
2002-11-18 16:12 ` Carlos O'Donell
2002-11-18 17:42 ` John David Anglin
2002-11-18 19:30 ` Carlos O'Donell
2002-11-18 19:44 ` John David Anglin
2002-11-11 1:21 ` Matthew Wilcox [this message]
2002-11-11 1:32 ` John David Anglin
2002-11-11 1:49 ` Carlos O'Donell
2002-11-11 3:45 ` John David Anglin
2002-11-11 4:26 ` John David Anglin
2002-11-11 15:03 ` Carlos O'Donell
2002-11-11 15:47 ` John David Anglin
2002-11-11 16:26 ` Carlos O'Donell
2002-11-11 17:25 ` John David Anglin
2002-11-11 17:37 ` Carlos O'Donell
2002-11-11 17:46 ` John David Anglin
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=20021111012129.A29998@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=carlos@baldric.uwo.ca \
--cc=jbailey@nisa.net \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.