| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
reportedly some programs (e.g. showkeys in the kbd package) use it.
|
| | |
|
| |
|
|
|
|
|
|
| |
it should now really match the kernel. some of the removed padding
corresponded to the difference between user and kernel sigset_t. the
space at the end was redundant with the uc_mcontext member and seems
to have been added as a result of misunderstanding glibc's definition
versus the kernel's.
|
| |
|
|
| |
these fields were wrongly copied from the kernel's ppc64 struct def
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
also handle the non-GNUC case where alignment attribute is not available
by simply omitting it. this will not cause problems except for
inclusion of mcontex_t/ucontext_t in application-defined structures,
since the natural alignment of the uc_mcontext member relative to the
start of ucontext_t is already correct. and shame on whoever designed
this for making it impossible to satisfy the ABI requirements without
GNUC extensions.
|
| | |
|
| |
|
