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 Date: Thu, 19 Oct 2000 12:27:01 -0400 From: Christopher Faylor To: cygwin AT sources DOT redhat DOT com Subject: Re: cygwin on a 386? Message-ID: <20001019122701.B32595@cygnus.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: cygwin AT sources DOT redhat DOT com References: <0056900013040104000002L042*@MHS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <0056900013040104000002L042*@MHS>; from jurgen.defurne@philips.com on Thu, Oct 19, 2000 at 08:36:09AM +0200 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. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com