From: P@draigBrady.com
To: Willy Tarreau <willy@w.ods.org>
Cc: linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
akpm@osdl.org
Subject: Re: i486 emu in mainline?
Date: Mon, 24 May 2004 10:08:08 +0100 [thread overview]
Message-ID: <40B1BB78.70508@draigBrady.com> (raw)
In-Reply-To: <20040523115936.GB16726@alpha.home.local>
Willy Tarreau wrote:
> On Sun, May 23, 2004 at 06:51:30AM -0400, Joseph Fannin wrote:
>
>>On Sun, May 23, 2004 at 10:29:12AM +0200, Willy Tarreau wrote:
>>
>>>On Sun, May 23, 2004 at 01:40:59AM +0200, Christoph Hellwig wrote:
>>>
>>>>These days gcc uses i486+ only instruction by default in libstdc++ so
>>>>most modern distros wouldn't work on i386 cpus anymore. To make it work
>>>>again Debian merged Willy Tarreau's patch to trap those and emulate them
>>>>on real i386 cpus. The patch is extremely non-invasive and would
>>>>certainly be usefull for mainline. Any reason not to include it?
>>
>>> - I couldn't emulate locks, so this will break on SMP systems, and so
>>> will it if you need to access some memory share with an external
>>> microcontroller or something like that.
>>
>> Does this mean that programs that use the NPTL will work on
>>non-SMP 386s?
>
> I have no idea. Why would NPTL not work on i386 ?
i386 doesn't have the necessary instructions.
It's my understanding that the following is not being maintained:
http://sources.redhat.com/ml/libc-hacker/2004-05/msg00019.html
Pádraig.
next prev parent reply other threads:[~2004-05-24 9:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 23:40 i486 emu in mainline? Christoph Hellwig
2004-05-23 0:20 ` Rene Rebe
2004-05-23 7:13 ` Arjan van de Ven
2004-05-23 8:44 ` Willy Tarreau
2004-05-23 9:13 ` Arjan van de Ven
2004-05-23 9:48 ` Willy Tarreau
2004-05-23 9:58 ` Arjan van de Ven
2004-05-23 11:49 ` Helge Hafting
2004-05-23 9:20 ` Andrew Morton
2004-05-23 17:11 ` Brian Gerst
2004-05-24 2:47 ` Herbert Xu
2004-05-27 21:03 ` Pavel Machek
2004-05-23 8:29 ` Willy Tarreau
2004-05-23 11:08 ` Alan Cox
2004-05-23 11:57 ` Willy Tarreau
2004-05-23 13:15 ` Alan Cox
2004-05-24 15:17 ` Jan-Benedict Glaw
2004-05-24 17:41 ` Alan Cox
2004-05-25 9:36 ` Jan-Benedict Glaw
2004-05-25 13:48 ` Alan Cox
[not found] ` <20040523105130.GA588@samarkand.rivenstone.net>
2004-05-23 11:59 ` Willy Tarreau
2004-05-24 9:08 ` P [this message]
2004-05-23 15:18 ` Jeff Garzik
2004-05-23 21:14 ` Alan Cox
2004-05-24 12:28 ` Maciej W. Rozycki
2004-05-25 17:21 ` Kronos
-- strict thread matches above, loose matches on Subject: below --
2004-05-25 17:03 Albert Cahalan
2004-05-25 22:43 ` Alan Cox
2004-10-10 20:33 Nathanael Nerode
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=40B1BB78.70508@draigBrady.com \
--to=p@draigbrady.com \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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.