MT string, to do next

[Ulrich Drepper]

ncm@cantrip.org writes:

> The 386 doesn't have a "lock" instruction,

That's not correct.  `lock' is available everywhere, from the 8086 on.

> (and on my NexGen P110, too).  

It's only your NexGen (this machine still lives)?

> Although the default x86 build must assume a 386 if not told otherwise, 

I wouldn't subscribe to this.  386 is completely dead, 486 maybe as
well.  I wouldn't care.

> multithreading must work right when running it, anyhow, even on an SMP 
> 686 box.  You can't get that behavior with inlines.

Of course you can.  You must not punish people who don't have obsolete
hardware.  If you really want you *can* write code which accounts for
this obsolete hardware but it definitely must not influence the
generally used code.

Beside, the `lock' prefix is only needed for SMP systems.

As far as I can see now the problem is only with oncompatible x86
clones (NexGen, infamous).  So maybe nobody should care at all and
Nathan tries to get a new machine.

-- 
---------------.      drepper at gnu.org  ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------