jyapayne/musl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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
commit 0c05bd3a9c
11 changed files with 47 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

8
src/linux/err.c
View file

@ -15,13 +15,13 @@ void vwarnx(const char *fmt, va_list ap)
putc('\n', stderr);
}
void verr(int status, const char *fmt, va_list ap)
_Noreturn void verr(int status, const char *fmt, va_list ap)
{
vwarn(fmt, ap);
exit(status);
}
void verrx(int status, const char *fmt, va_list ap)
_Noreturn void verrx(int status, const char *fmt, va_list ap)
{
vwarnx(fmt, ap);
exit(status);
@ -43,7 +43,7 @@ void warnx(const char *fmt, ...)
va_end(ap);
}
void err(int status, const char *fmt, ...)
_Noreturn void err(int status, const char *fmt, ...)
{
va_list ap;
va_start(ap, fmt);
@ -51,7 +51,7 @@ void err(int status, const char *fmt, ...)
va_end(ap);
}
void errx(int status, const char *fmt, ...)
_Noreturn void errx(int status, const char *fmt, ...)
{
va_list ap;
va_start(ap, fmt);