Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | don't reject unknown/future flags in sigaltstack, allow SS_AUTODISARM | Rich Felker | 2019-03-05 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | historically, and likely accidentally, sigaltstack was specified to fail with EINVAL if any flag bit other than SS_DISABLE was set. the resolution of Austin Group issue 1187 fixes this so that the requirement is only to fail for SS_ONSTACK (which cannot be set) or "invalid" flags. Linux fails on the kernel side for invalid flags, but historically accepts SS_ONSTACK as a no-op, so it needs to be rejected in userspace still. with this change, the Linux-specific SS_AUTODISARM, provided since commit 9680e1d03a794b0e0d5815c749478228ed40a36d but unusable due to rejection at runtime, is now usable. | ||||
* | use restrict everywhere it's required by c99 and/or posix 2008 | Rich Felker | 2012-09-06 | 1 | -1/+1 |
| | | | | | | | | to deal with the fact that the public headers may be used with pre-c99 compilers, __restrict is used in place of restrict, and defined appropriately for any supported compiler. we also avoid the form [restrict] since older versions of gcc rejected it due to a bug in the original c99 standard, and instead use the form *restrict. | ||||
* | global cleanup to use the new syscall interface | Rich Felker | 2011-03-20 | 1 | -1/+1 |
| | |||||
* | make sigaltstack work (missing macros in signal.h, error conditions) | Rich Felker | 2011-03-10 | 1 | -1/+11 |
| | |||||
* | initial check-in, version 0.5.0 v0.5.0 | Rich Felker | 2011-02-12 | 1 | -0/+8 |