From: Chris Wedgwood <cw@f00f.org>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
William Stearns <wstearns@pobox.com>
Subject: Re: [uml-devel] glibc and NPTL, problem, workarounds, etc.
Date: Sun, 12 Sep 2004 12:32:37 -0700 [thread overview]
Message-ID: <20040912193237.GA8253@taniwha.stupidest.org> (raw)
In-Reply-To: <200409122127.12738.blaisorblade_spam@yahoo.it>
On Sun, Sep 12, 2004 at 09:27:12PM +0200, BlaisorBlade wrote:
> Are you sure? I remember that NPTL needs using some new instructions
> of i686 (maybe CMOVxx) for futexes, to be atomic.
i586 and later i486 will suffice
> However, if I'm wrong, we could even pretend to be i386.
NPTL can be made to work too there I'm told, with a little more
effort. I'm not sure if anyone will ever bother...
> Well, you compile Gentoo for your own processor - you might maybe
> even enable -mregparm for everything (which even breaks binary
> compatibility everything).
i was thinking gentoo on a i585 would maybe build /lib/tls/i586
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-09-12 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 19:02 [uml-devel] glibc and NPTL, problem, workarounds, etc William Stearns
2004-09-08 20:08 ` Steven Pritchard
2004-09-12 18:20 ` BlaisorBlade
2004-09-12 19:02 ` Chris Wedgwood
2004-09-12 19:27 ` BlaisorBlade
2004-09-12 19:32 ` Chris Wedgwood [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=20040912193237.GA8253@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=wstearns@pobox.com \
/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