From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Matthew Wilcox <willy@debian.org>,
parisc-linux@lists.parisc-linux.org, tausq@debian.org,
jbailey@nisa.net
Subject: Re: [parisc-linux] glibc 2.3.1 - It's alive! - patches
Date: Sun, 10 Nov 2002 20:49:35 -0500 [thread overview]
Message-ID: <20021111014935.GB13575@systemhalted> (raw)
In-Reply-To: <200211110132.gAB1WK8T004703@hiauly1.hia.nrc.ca>
>
> Paul Bame was working on getting HP to release their long double library
> code. I haven't heard what the status is. If he gets the code, then it
> should be relatively straight forward to integrate into libgcc and use
> the same code as for hpux. Can glibc handle 128-bit long doubles as
> that's the size long doubles will be if we get the code?
>
> There are two tests in the libstdc++-v3 suite that fail because of this.
> However, there can't be much in the way of real world code that actually
> uses long doubles.
>
It looks we have the framework. The glibc tree has sysdeps/ieee754/ldbl-128
which looks to be used by hppa and sparc64. The code was last touched by
Jakub Jelinek in 2002-09-09 (cleaning up some cruft). ldlb-128 does get
parsed as one of the generic-dirs in Make-dist. For all intents and
purposes we have soft-emulated support :)
c.
next prev parent reply other threads:[~2002-11-11 1:50 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
2002-11-11 1:32 ` John David Anglin
2002-11-11 1:49 ` Carlos O'Donell [this message]
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=20021111014935.GB13575@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=jbailey@nisa.net \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.org \
--cc=willy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox