musl/include/signal.h, branch master musl - an implementation of the standard library for Linux-based systems signal.h: add new sa_flags from linux v5.11 2022年03月08日T22:19:49+00:00 Szabolcs Nagy nsz@port70.net 2021年03月17日T19:19:27+00:00 e99c4258275507c576d7d5bebdba1a8aadf120c4 see linux commit a54f0dfda754c5cecc89a14dab68a3edc1e497b5 signal: define the SA_UNSUPPORTED bit in sa_flags linux commit 6ac05e832a9e96f9b1c42a8917cdd317d7b6c8fa signal: define the SA_EXPOSE_TAGBITS bit in sa_flags Note: SA_ is in the posix reserved namespace so these linux specific flags can be exposed when compiling for posix.
see
 linux commit a54f0dfda754c5cecc89a14dab68a3edc1e497b5
 signal: define the SA_UNSUPPORTED bit in sa_flags
 linux commit 6ac05e832a9e96f9b1c42a8917cdd317d7b6c8fa
 signal: define the SA_EXPOSE_TAGBITS bit in sa_flags
Note: SA_ is in the posix reserved namespace so these linux specific flags
can be exposed when compiling for posix.
signal.h: add SYS_USER_DISPATCH si_code value from linux v5.11 2022年03月08日T22:19:48+00:00 Szabolcs Nagy nsz@port70.net 2021年03月07日T22:20:54+00:00 993cccce13ba3ae0432cb06eacd2e7f55a090952 see linux commit 1d7637d89cfce54a4f4a41c2325288c2f47470e8 signal: Expose SYS_USER_DISPATCH si_code type
see
 linux commit 1d7637d89cfce54a4f4a41c2325288c2f47470e8
 signal: Expose SYS_USER_DISPATCH si_code type
signal.h: add si_code values for SIGSYS 2022年03月08日T22:19:46+00:00 Szabolcs Nagy nsz@port70.net 2021年03月07日T22:15:11+00:00 3dcbd896907d9d474da811b7c6b769342abaf651 unlike other si_code defines, SYS_ is not in the posix reserved namespace which is likely the reason why SYS_SECCOMP was previously missing (was new in linux v3.5).
unlike other si_code defines, SYS_ is not in the posix reserved namespace
which is likely the reason why SYS_SECCOMP was previously missing (was new
in linux v3.5).
signal.h: add MTE specific SIGSEGV codes from linux v5.10 2021年02月15日T14:16:06+00:00 Szabolcs Nagy nsz@port70.net 2020年12月19日T22:12:50+00:00 87b8f14811abe5b707ebe109296bcb0efbebcce2 add synchronouse and asynchronous tag check failure codes, see linux commit 74f1082487feb90bbf880af14beb8e29c3030c9f arm64: mte: Add specific SIGSEGV codes
add synchronouse and asynchronous tag check failure codes, see
 linux commit 74f1082487feb90bbf880af14beb8e29c3030c9f
 arm64: mte: Add specific SIGSEGV codes
add support for SIGEV_THREAD_ID timers 2020年10月29日T03:00:08+00:00 James Y Knight jyknight@google.com 2019年07月01日T01:55:20+00:00 7c71792e87691451f2a6b76348e83ad1889f1dcb This is like SIGEV_SIGNAL, but targeted to a particular thread's tid, rather than the process.
This is like SIGEV_SIGNAL, but targeted to a particular thread's
tid, rather than the process.
add time64 symbol name redirects to public headers, under arch control 2019年10月28日T23:26:52+00:00 Rich Felker dalias@aerifal.cx 2019年07月31日T19:24:58+00:00 1febd21d3fb7b78f6fc13e48b3ff2a396a607a15 a _REDIR_TIME64 macro is introduced, which the arch's alltypes.h is expected to define, to control redirection of symbol names for interfaces that involve time_t and derived types. this ensures that object files will only be linked to libc interfaces matching the ABI whose headers they were compiled against. along with time32 compat shims, which will be introduced separately, the redirection also makes it possible for a single libc (static or shared) to be used with object files produced with either the old (32-bit time_t) headers or the new ones after 64-bit time_t switchover takes place. mixing of such object files (or shared libraries) in the same program will also be possible, but must be done with care; ABI between libc and a consumer of the libc interfaces is guaranteed to match by the the symbol name redirection, but pairwise ABI between consumers of libc that define interfaces between each other in terms of time_t is not guaranteed to match. this change adds a dependency on an additional "GNU C" feature to the public headers for existing 32-bit archs, which is generally undesirable; however, the feature is one which glibc has depended on for a long time, and thus which any viable alternative compiler is going to need to provide. 64-bit archs are not affected, nor will future 32-bit archs be, regardless of whether they are "new" on the kernel side (e.g. riscv32) or just newly-added (e.g. a new sparc or xtensa port). the same applies to newly-added ABIs for existing machine-level archs.
a _REDIR_TIME64 macro is introduced, which the arch's alltypes.h is
expected to define, to control redirection of symbol names for
interfaces that involve time_t and derived types. this ensures that
object files will only be linked to libc interfaces matching the ABI
whose headers they were compiled against.
along with time32 compat shims, which will be introduced separately,
the redirection also makes it possible for a single libc (static or
shared) to be used with object files produced with either the old
(32-bit time_t) headers or the new ones after 64-bit time_t switchover
takes place. mixing of such object files (or shared libraries) in the
same program will also be possible, but must be done with care; ABI
between libc and a consumer of the libc interfaces is guaranteed to
match by the the symbol name redirection, but pairwise ABI between
consumers of libc that define interfaces between each other in terms
of time_t is not guaranteed to match.
this change adds a dependency on an additional "GNU C" feature to the
public headers for existing 32-bit archs, which is generally
undesirable; however, the feature is one which glibc has depended on
for a long time, and thus which any viable alternative compiler is
going to need to provide. 64-bit archs are not affected, nor will
future 32-bit archs be, regardless of whether they are "new" on the
kernel side (e.g. riscv32) or just newly-added (e.g. a new sparc or
xtensa port). the same applies to newly-added ABIs for existing
machine-level archs.
add TRAP_UNK si_code to signal.h from linux v4.18 2018年12月10日T03:29:07+00:00 Szabolcs Nagy nsz@port70.net 2018年08月22日T17:10:55+00:00 ca73bea05d83f3775cf1dd6c8135a69a20c78bf4 used for undiagnosed trap exceptions where linux previously set si_code to 0. new in linux commit db78e6a0a6f9f7d7277965600eeb1a5b3a6f55a8
used for undiagnosed trap exceptions where linux previously set si_code
to 0. new in linux commit db78e6a0a6f9f7d7277965600eeb1a5b3a6f55a8
remove spurious const keyword in sigqueue declaration 2018年03月10日T23:19:41+00:00 Rich Felker dalias@aerifal.cx 2018年03月10日T23:03:17+00:00 f9c2498fee1c94adf00e788863d2d4544d1d1ec0 this must have been taken from POSIX without realizing that it was meaningless. the resolution to Austin Group issue #844 removed it from the standard.
this must have been taken from POSIX without realizing that it was
meaningless. the resolution to Austin Group issue #844 removed it from
the standard.
signal.h: add missing SIGTRAP si_codes 2018年02月22日T23:46:31+00:00 Szabolcs Nagy nsz@port70.net 2017年11月26日T23:20:38+00:00 38e81ddc0440ecc61f6fa9faf9225b91c9c8017c TRAP_BRANCH and TRAP_HWBKPT new in linux commit da654b74bda14c45a7d98c731bf3c1a43b6b74e2
TRAP_BRANCH and TRAP_HWBKPT new in linux commit
da654b74bda14c45a7d98c731bf3c1a43b6b74e2
add SS_AUTODISARM sigaltstack ss_flags from linux v4.7 to signal.h 2016年08月30日T19:58:25+00:00 Szabolcs Nagy nsz@port70.net 2016年08月20日T15:04:44+00:00 9680e1d03a794b0e0d5815c749478228ed40a36d only matters if swapcontext is used in a signal handler running on an altstack, new in linux commit 2a74213838104a41588d86fd5e8d344972891ace
only matters if swapcontext is used in a signal handler running on an
altstack, new in linux commit 2a74213838104a41588d86fd5e8d344972891ace

AltStyle によって変換されたページ (->オリジナル) /