fluencelabs/musl
1
0
Fork 0
mirror of https://github.com/fluencelabs/musl synced 2025-06-23 03:31:55 +00:00
Code Issues Projects Releases Wiki Activity

further use of _Noreturn, for non-plain-C functions

Browse Source 
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.
This commit is contained in:
Rich Felker
2012-09-06 23:34:10 -04:00
parent 453059571c
commit 0c05bd3a9c
11 changed files with 47 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
include/assert.h
View File

@ -1,5 +1,12 @@
#undef assert
#if __STDC_VERSION__ >= 201112L
#elif defined(__GNUC__)
#define _Noreturn __attribute__((__noreturn__))
#else
#define _Noreturn
#endif
#ifdef NDEBUG
#define assert(x) (void)0
#else
@ -10,7 +17,7 @@
extern "C" {
#endif
void __assert_fail (const char *, const char *, int, const char *);
_Noreturn void __assert_fail (const char *, const char *, int, const char *);
#ifdef __cplusplus
}