2011-02-12 05:22:29 +00:00
|
|
|
#ifndef _SETJMP_H
|
|
|
|
#define _SETJMP_H
|
|
|
|
|
|
|
|
#ifdef __cplusplus
|
|
|
|
extern "C" {
|
|
|
|
#endif
|
|
|
|
|
2012-09-08 03:13:55 +00:00
|
|
|
#include <features.h>
|
2012-09-07 03:12:27 +00:00
|
|
|
|
2011-02-12 05:22:29 +00:00
|
|
|
#include <bits/setjmp.h>
|
|
|
|
|
2013-07-24 06:17:02 +00:00
|
|
|
typedef struct __jmp_buf_tag {
|
|
|
|
__jmp_buf __jb;
|
|
|
|
unsigned long __fl;
|
|
|
|
unsigned long __ss[128/sizeof(long)];
|
|
|
|
} jmp_buf[1];
|
2011-02-14 23:41:25 +00:00
|
|
|
|
|
|
|
#if defined(_POSIX_SOURCE) || defined(_POSIX_C_SOURCE) \
|
2012-05-23 01:52:08 +00:00
|
|
|
|| defined(_XOPEN_SOURCE) || defined(_GNU_SOURCE) \
|
|
|
|
|| defined(_BSD_SOURCE)
|
2013-07-24 06:17:02 +00:00
|
|
|
typedef jmp_buf sigjmp_buf;
|
2011-02-14 23:41:25 +00:00
|
|
|
int sigsetjmp (sigjmp_buf, int);
|
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-07 03:34:10 +00:00
|
|
|
_Noreturn void siglongjmp (sigjmp_buf, int);
|
2011-02-14 23:41:25 +00:00
|
|
|
#endif
|
2011-02-12 05:22:29 +00:00
|
|
|
|
2012-05-23 01:52:08 +00:00
|
|
|
#if defined(_XOPEN_SOURCE) || defined(_GNU_SOURCE) \
|
|
|
|
|| defined(_BSD_SOURCE)
|
2011-02-12 05:22:29 +00:00
|
|
|
int _setjmp (jmp_buf);
|
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-07 03:34:10 +00:00
|
|
|
_Noreturn void _longjmp (jmp_buf, int);
|
2011-02-14 23:41:25 +00:00
|
|
|
#endif
|
|
|
|
|
|
|
|
int setjmp (jmp_buf);
|
2012-09-07 03:12:27 +00:00
|
|
|
_Noreturn void longjmp (jmp_buf, int);
|
2011-02-12 05:22:29 +00:00
|
|
|
|
|
|
|
#define setjmp setjmp
|
|
|
|
|
|
|
|
#ifdef __cplusplus
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#endif
|