Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: jurgen DOT defurne AT philips DOT com To: Subject: Re: cygwin on a 386? Message-ID: <0056900013040104000002L042*@MHS> Date: Thu, 19 Oct 2000 08:36:09 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; name="MEMO 10/19/00 08:28:00" Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id CAA08108 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. Jurgen cgf AT redhat DOT com@SMTP AT sources DOT redhat DOT com on 19/10/2000 03:33:54 Please respond to cygwin AT sources DOT redhat DOT com@SMTP Sent by: cygwin-owner AT sources DOT redhat DOT com To: cygwin AT sources DOT redhat DOT com@SMTP cc: Subject: cygwin on a 386? Classification: I am contemplating adding some more assembly language stuff to Cygwin but on reading the Microsoft docs, it became apparent that some of the cruft in Windows 95 is due to its ability to run on a 80386 platform. So, things like InterlockedIncrement and InterlockedExchange, which are relatively simple on NT are amazingly complicated on Windows 95. So, my question is, has anyone ever used cygwin on a 80386 system? I'm wondering if it works at all right now. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com