Mail Archives: cygwin/2000/10/21/01:18:44
On Fri, 20 Oct 2000 08:58:54 +0200, jurgen DOT defurne AT philips DOT com wrote:
>On Thu, Oct 19, 2000 at 12:27:01PM -0400, Christopher Faylor wrote:
>>On Thu, Oct 19, 2000 at 08:36:09AM +0200, jurgen DOT defurne AT philips DOT com wrote:
>>>These instructions have their equivalent since the first 80x86.
>>> LOCK
>>> INC dest
>>>
>>> LOCK
>>> XCHG dest,src
>>>
>>>Of course, these operate at most between a register and memory, not
>>>between memory and memory.
>>
>>Are you answering my question about whether Cygwin works on a 386?
>>Somehow I can't figure this out from your message. You seem to be
>>instructing me in assembly language, which wasn't what I was asking
>>for.
>
>What I mention is this : I presume that the interlocking mechanism is
>just to isolate a variable from being updated by another task, while
>the current task should do it. This has been possible since the early
>8086. What I wondered is why the before mentioned instructions go
>through such great lengths to provide the necessary mechanisms.
The instruction in question is CMPXCHG. It's only available on a 486
and above:
http://developer.intel.com/design/intarch/techinfo/Pentium/instsum.htm
I'm still waiting for someone to inform me that Cygwin works fine on a
386...
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -