RepoMirrors
/
musl
mirror of git://git.musl-libc.org/musl
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
musl/include/assert.h

24 lines
428 B
C
Raw Normal View History

default features: make musl usable without feature test macros the old behavior of exposing nothing except plain ISO C can be obtained by defining __STRICT_ANSI__ or using a compiler option (such as -std=c99) that predefines it. the new default featureset is POSIX with XSI plus _BSD_SOURCE. any explicit feature test macros will inhibit the default. installation docs have also been updated to reflect this change.
2012-09-08 03:13:55 +00:00
#include <features.h>
initial check-in, version 0.5.0
2011-02-12 05:22:29 +00:00
default features: make musl usable without feature test macros the old behavior of exposing nothing except plain ISO C can be obtained by defining __STRICT_ANSI__ or using a compiler option (such as -std=c99) that predefines it. the new default featureset is POSIX with XSI plus _BSD_SOURCE. any explicit feature test macros will inhibit the default. installation docs have also been updated to reflect this change.
2012-09-08 03:13:55 +00:00
#undef assert
further use of _Noreturn, for non-plain-C functions note that POSIX does not specify these functions as _Noreturn, because POSIX is aligned with C99, not the new C11 standard. when POSIX is eventually updated to C11, it will almost surely give these functions the _Noreturn attribute. for now, the actual _Noreturn keyword is not used anyway when compiling with a c99 compiler, which is what POSIX requires; the GCC __attribute__ is used instead if it's available, however. in a few places, I've added infinite for loops at the end of _Noreturn functions to silence compiler warnings. presumably __buildin_unreachable could achieve the same thing, but it would only work on newer GCCs and would not be portable. the loops should have near-zero code size cost anyway. like the previous _Noreturn commit, this one is based on patches contributed by philomath.
2012-09-07 03:34:10 +00:00
initial check-in, version 0.5.0
2011-02-12 05:22:29 +00:00
#ifdef NDEBUG
#define assert(x) (void)0
#else
assert() is supposed to have type void
2012-10-17 06:47:11 +00:00
#define assert(x) ((void)((x) || (__assert_fail(#x, __FILE__, __LINE__, __func__),0)))
initial check-in, version 0.5.0
2011-02-12 05:22:29 +00:00
#endif
do not define static_assert macro for pre-C11 compilers some software simply uses static_assert if the macro is defined, and this breaks if the compiler does not recognize the _Static_assert keyword used to define it.
2016-02-12 15:11:40 +00:00
#if __STDC_VERSION__ >= 201112L && !defined(__cplusplus)
add static_assert and hide noreturn, alignas, alignof from C++ add static_assert and protect the other new C11 keyword macros with #ifndef __cplusplus so they don't conflict with C++ keywords.
2014-08-26 15:42:15 +00:00
#define static_assert _Static_assert
#endif
initial check-in, version 0.5.0
2011-02-12 05:22:29 +00:00
#ifdef __cplusplus
extern "C" {
#endif
restore _Noreturn to __assert_fail this reverts commit 2c1f8fd5da3306fd7c8a2267467e44eb61f12dd4. without the _Noreturn attribute, the compiler cannot use asserts to perform reachability/range analysis. this leads to missed optimizations and spurious warnings. the original backtrace problem that prompted the removal of _Noreturn was not clearly documented at the time, but it seems to happen only when libc was built without -g, which also breaks many other backtracing cases.
2016-08-30 20:39:54 +00:00
_Noreturn void __assert_fail (const char *, const char *, int, const char *);
initial check-in, version 0.5.0
2011-02-12 05:22:29 +00:00
#ifdef __cplusplus
}
#endif