Determines if the atomic operations on all objects of the typeA (the type of the object pointed to byobj) are lock-free. In any given program execution, the result of callingatomic_is_lock_free is the same for all pointers of the same type.

This is ageneric function defined for allatomic object typesA. The argument is pointer to a volatile atomic type to accept addresses of both non-volatile andvolatile (e.g. memory-mapped I/O) atomic objects, and volatile semantic is preserved when applying this operation to volatile atomic objects.

It is unspecified whether the name of a generic function is a macro or an identifier declared with external linkage. If a macro definition is suppressed in order to access an actual function (e.g. parenthesized like(atomic_is_lock_free)(...)), or a program defines an external identifier with the name of a generic function, the behavior is undefined.

[edit]Parameters

[edit]Return value

true if the operations on all objects of the typeA are lock-free,false otherwise.

[edit]Example

#include <stdio.h>#include <stdatomic.h> _Atomicstruct A{int a[100];} a;_Atomicstruct B{int x, y;} b;int main(void){printf("_Atomic struct A is lock free? %s\n",             atomic_is_lock_free(&a)?"true":"false");printf("_Atomic struct B is lock free? %s\n",             atomic_is_lock_free(&b)?"true":"false");}

_Atomic struct A is lock free? false_Atomic struct B is lock free? true

[edit]Defect reports

The following behavior-changing defect reports were applied retroactively to previously published C standards.

[edit]References

[edit]See also

• In other languages

• العربية
• Česky
• Deutsch
• Español
• Français
• Italiano
• 日本語
• 한국어
• Polski
• Português
• Русский
• Türkçe
• 中文