unlike the previous definition, NSIG/_NSIG is supposed to be one more
than the highest signal number. adding this will allow simplifying
libc-internal code that makes signal-related syscalls, which can be
done as a later step. some apps might use it too; while this usage is
questionable, it's at least not insane.
#define SIGPWR 30
#define SIGSYS 31
#define SIGUNUSED SIGSYS
+
+#define _NSIG 65
#define SIGPWR 30
#define SIGSYS 31
#define SIGUNUSED SIGSYS
+
+#define _NSIG 65
#define SIGPWR 30
#define SIGSYS 31
#define SIGUNUSED SIGSYS
+
+#define _NSIG 65
#define SIGXCPU 30
#define SIGXFSZ 31
#define SIGUNUSED SIGSYS
+
+#define _NSIG 129
#define SIGPWR 30
#define SIGSYS 31
#define SIGUNUSED SIGSYS
+
+#define _NSIG 65
#define SIGPWR 30
#define SIGSYS 31
#define SIGUNUSED SIGSYS
+
+#define _NSIG 65
int sigisemptyset(const sigset_t *);
#define SA_NOMASK SA_NODEFER
#define SA_ONESHOT SA_RESETHAND
+#define NSIG _NSIG
#endif
#include <bits/signal.h>