ivmai/libatomic_ops

determining features

dotnwat opened this issue · 3 comments

dotnwat commented

Hi, is there a way to see which sysdep has been used in the compiled library? for instance, i'd like to know if when i compile i'm getting something efficient vs the backup mutex implementation.

ivmai commented

Hello Noah,

sysdep depends on the architecture and compiler, e.g. gcc/x86.h

CAS emulated only if no H/W CAS but AO_REQUIRE_CAS defined.

Mutex implementation uses AO_pt_lock defined in src/atomic_ops.c (use -D AO_NO_PTHREADS to fail compile/link if mutex implementation is used.

Regards,
Ivan

Tue, 6 Aug 2013, 7:06 -07:00 from Noah Watkins notifications@github.com:

Hi, is there a way to see which sysdep has been used in the compiled library? for instance, i'd like to know if when i compile i'm getting something efficient vs the backup mutex implementation.
—
Reply to this email directly or view it on GitHub .

dotnwat commented

Thanks thats really useful. Im specifically interested in x86 and clang.
On Aug 8, 2013 2:04 PM, "Ivan Maidanski" notifications@github.com wrote:

Hello Noah,

sysdep depends on the architecture and compiler, e.g. gcc/x86.h

CAS emulated only if no H/W CAS but AO_REQUIRE_CAS defined.

Mutex implementation uses AO_pt_lock defined in src/atomic_ops.c (use -D
AO_NO_PTHREADS to fail compile/link if mutex implementation is used.

Regards,
Ivan

Tue, 6 Aug 2013, 7:06 -07:00 from Noah Watkins notifications@github.com:

Hi, is there a way to see which sysdep has been used in the compiled
library? for instance, i'd like to know if when i compile i'm getting
something efficient vs the backup mutex implementation.
—
Reply to this email directly or view it on GitHub .

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-22355684
.

ivmai commented

See also auto-generated tests/list_atomic.c (I have improved it recently)