From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org, debian-hppa@lists.debian.org
Subject: Re: [parisc-linux] [Status] hppa's userspace in 2004 (looking back)
Date: Tue, 6 Jan 2004 00:39:25 -0500 [thread overview]
Message-ID: <20040106053924.GC14464@systemhalted> (raw)
In-Reply-To: <200401051848.i05Imt6p005065@hiauly1.hia.nrc.ca>
On Mon, Jan 05, 2004 at 01:48:54PM -0500, John David Anglin wrote:
> As usual, I expect there will be many ups and downs in the process.
> So, we won't get as far as we would like.
>
> > jda, you mentioned that the libstdc++ testsuite could be examined in
> > order to fix some of our failures.
>
> Yes, these need to be looked at before 3.4 is released. Some appear
> to be related to long double support. Just guessing, but I think the
> rest are locale or glibc related.
Does this seem like a reasonable triage list?
a. gdb.
b. atomic kernel ops.
c. libstdc++ failures.
c.
next prev parent reply other threads:[~2004-01-06 5:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 17:21 [parisc-linux] [Status] hppa's userspace in 2004 (looking back) Carlos O'Donell
2004-01-05 18:48 ` John David Anglin
2004-01-05 18:48 ` John David Anglin
2004-01-06 5:39 ` Carlos O'Donell [this message]
2004-01-06 6:16 ` John David Anglin
2004-01-06 15:48 ` Carlos O'Donell
2004-01-06 15:48 ` Carlos O'Donell
2004-01-06 6:16 ` John David Anglin
2004-01-06 5:39 ` Carlos O'Donell
2004-01-05 19:33 ` [parisc-linux] " Matthew Wilcox
2004-01-05 19:33 ` Matthew Wilcox
2004-01-05 21:45 ` Helge Deller
2004-01-05 21:45 ` Helge Deller
2004-01-06 0:00 ` Christopher Strong
2004-01-06 5:32 ` Carlos O'Donell
2004-01-08 8:06 ` [parisc-linux] " Joel Soete
2004-01-09 20:37 ` Joel Soete
2004-01-09 20:37 ` Joel Soete
2004-01-12 17:51 ` Joel Soete
2004-01-12 17:51 ` Joel Soete
2004-01-08 8:06 ` Joel Soete
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 17:21 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=20040106053924.GC14464@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=debian-hppa@lists.debian.org \
--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 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.