summaryrefslogtreecommitdiff
path: root/include/setjmp.h
diff options
context:
space:
mode:
authorRich Felker <dalias@aerifal.cx>2012-09-06 23:34:10 -0400
committerRich Felker <dalias@aerifal.cx>2012-09-06 23:34:10 -0400
commit0c05bd3a9c165cf2f0b9d6fa23a1f96532ddcdb3 (patch)
tree124c1d65e338abece7cf55c95cbc8195be94fe2f /include/setjmp.h
parent453059571c9dc84dd168631eced25ec2d7afd98e (diff)
downloadmusl-0c05bd3a9c165cf2f0b9d6fa23a1f96532ddcdb3.tar.gz
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.
Diffstat (limited to 'include/setjmp.h')
-rw-r--r--include/setjmp.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/include/setjmp.h b/include/setjmp.h
index 8ec5c6f1..e5877b44 100644
--- a/include/setjmp.h
+++ b/include/setjmp.h
@@ -24,14 +24,14 @@ typedef struct {
unsigned long __ss[128/sizeof(long)];
} sigjmp_buf[1];
int sigsetjmp (sigjmp_buf, int);
-void siglongjmp (sigjmp_buf, int);
+_Noreturn void siglongjmp (sigjmp_buf, int);
#endif
#if defined(_XOPEN_SOURCE) || defined(_GNU_SOURCE) \
|| defined(_BSD_SOURCE)
int _setjmp (jmp_buf);
-void _longjmp (jmp_buf, int);
+_Noreturn void _longjmp (jmp_buf, int);
#endif