From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Cc: "Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: N32 sigset and __COMPAT_ENDIAN_SWAP__
Date: Thu, 08 Jun 2006 21:15:56 -0400 [thread overview]
Message-ID: <4488CBCC.4090405@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606081706310.7925@digraph.polyomino.org.uk>
Joseph S. Myers wrote:
>
> I might conclude that barely anybody is *yet* using NPTL on 64-bit MIPS at
> all, for either endianness, given that most of the problems I've been
> finding, in glibc as well as the kernel, don't seem endian-specific and
> would probably show up in a glibc testsuite run for either endianness.
> MIPS64 NPTL is very new and seems to do a good job of showing up bugs in
> the three syscall interfaces.
I'm actually going to start running some automated builds of a nptl/o32 and
nptl/n32 userland over the next few days. If you have any patches that need
testing to correct known oddities, I can give them a run in these builds.
--Kumba
--
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees
"Such is oft the course of deeds that move the wheels of the world: small hands
do them because they must, while the eyes of the great are elsewhere." --Elrond
prev parent reply other threads:[~2006-06-09 1:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 1:36 N32 sigset and __COMPAT_ENDIAN_SWAP__ Joseph S. Myers
2006-06-08 2:25 ` Kumba
2006-06-08 2:28 ` Daniel Jacobowitz
2006-06-08 2:38 ` Kumba
2006-06-08 2:45 ` Kumba
2006-06-08 16:51 ` Ralf Baechle
2006-06-08 17:03 ` Daniel Jacobowitz
2006-06-08 17:36 ` Ralf Baechle
2006-06-08 17:12 ` Joseph S. Myers
2006-06-09 1:15 ` Kumba [this message]
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=4488CBCC.4090405@gentoo.org \
--to=kumba@gentoo.org \
--cc=joseph@codesourcery.com \
--cc=linux-mips@linux-mips.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