Rich Felker 0c05bd3a9c 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-06 23:34:10 -04:00
..
2012-07-02 22:49:25 -04:00
2012-07-12 22:20:36 -04:00
2011-02-12 00:22:29 -05:00
2011-06-08 16:41:44 -04:00
2011-02-12 00:22:29 -05:00
2011-02-12 00:22:29 -05:00
2011-02-12 00:22:29 -05:00
2011-09-12 00:00:30 -04:00
2011-07-30 21:11:31 -04:00
2011-02-12 00:22:29 -05:00
2011-02-12 00:22:29 -05:00
2011-02-12 00:22:29 -05:00