Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Thu, 12 Dec 2002 11:30:49 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: quandary with pthreads
Message-ID: <20021212163049.GC10952@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20021212060316 DOT GA10952 AT redhat DOT com> <NCBBIHCHBLCMLBLOBONKKEHDDJAA DOT g DOT r DOT vansickle AT worldnet DOT att DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NCBBIHCHBLCMLBLOBONKKEHDDJAA.g.r.vansickle@worldnet.att.net>
User-Agent: Mutt/1.5.1i

On Thu, Dec 12, 2002 at 01:37:37AM -0600, Gary R. Van Sickle wrote:
>Ok, attached is what I'd try if I was set up to try it.  I've found that you
>pretty much always need the "volatile" after the __asm__, or the newer gccs want
>to optimize your assembly away, even if they should be able to tell that you've
>got side-effects.

AFAIK, there is a volatile after the __asm__.

How about a standard unified diff so that it is easy to see what you changed?

cgf