On Mon, Nov 30, 2009 at 04:00:08PM +0100, Steve wrote:

> > > > On Mon, Nov 30, 2009 at 02:55:00PM +0100, Steve wrote:
> > > >
> > > > > > *) Feature: the --with-libatomic[=DIR] option in the
> > configure.
> > > > > > Thanks to W-Mark Kubacki.
> > > > > >
> > > > > What is this libatomic? Is it this here ->
> > > > http://www.hpl.hp.com/research/linux/atomic_ops/
> > > >
> > > > Yes.
> > > >
> > > Is that needed if one is using GCC >= 4.1? Or is this already used (in
> > some way) by this here:
> > > > *) Feature: GCC 4.1+ built-in atomic operations usage.
> > > > Thanks to W-Mark Kubacki.
> >
> > If GCC supports atomic operations, then nginx uses them. Otherwise, it
> > uses
> > own atomic operations for i386, amd64, sparc32/64, ppc32/64.
> >
> > You may force to use libatomic, if you do not like GCC atomic operations.
> >
> Okay. I understand. Is there any benefit using libatomic?

GCC built-ins are better at least for i386 and amd64.
libatomic is better for ARM:
http://nginx.org/pipermail/nginx/2009-September/015726.html


--
Igor Sysoev
http://sysoev.ru/en/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx