From: Rich Felker <dalias@aerifal.cx>
Date: Fri, 7 Sep 2012 03:34:10 +0000 (-0400)
Subject: further use of _Noreturn, for non-plain-C functions
X-Git-Url: http://nsz.repo.hu/git/?a=commitdiff_plain;ds=sidebyside;h=0c05bd3a9c165cf2f0b9d6fa23a1f96532ddcdb3;hp=0c05bd3a9c165cf2f0b9d6fa23a1f96532ddcdb3;p=musl

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.
---