This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
RE: quandary with pthreads
- From: Thomas Pfaff <tpfaff at gmx dot net>
- To: "Gary R. Van Sickle" <g dot r dot vansickle at worldnet dot att dot net>
- Cc: cygwin-developers at cygwin dot com
- Date: Thu, 12 Dec 2002 10:45:42 +0100 (Westeuropäische Normalzeit)
- Subject: RE: quandary with pthreads
Yup, that did the trick.
Chris, can you take a look at it ?
Thomas
On Thu, 12 Dec 2002, 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.
>
> --
> Gary R. Van Sickle
> Brewer. Patriot.
>
> > -----Original Message-----
> > From: cygwin-developers-owner@cygwin.com
> > [mailto:cygwin-developers-owner@cygwin.com]On Behalf Of Christopher
> > Faylor
> > Sent: Thursday, December 12, 2002 12:03 AM
> > To: cygwin-developers@cygwin.com
> > Subject: Re: quandary with pthreads
> >
> >
> > On Wed, Dec 11, 2002 at 11:53:03PM -0600, Gary R. Van Sickle wrote:
> > >>I have created assembler versions for the Interlocked functions that
> > >>work fine unless they are made inline (see attachment). Maybe
> someone
> > >>with a better understanding of gcc inline assembler might have a
> look
> > >>at it).
> > >
> > >I may have the painfully-acquired honor of fitting that description.
> > >How were you trying to inline them? Essentially as-is? If so, I
> just
> > >may be able to help.
> >
> > The routines in question are in winbase.h. I took inspiration for
> most
> > of them from linux.
> >
> > cgf
>
>