summaryrefslogtreecommitdiff
path: root/include/sys (follow)
AgeCommit message (Collapse)Author
2026-03-13Fix compilation under clangjvoisin
Makes uses of _FORTIFY_INLINE and _FORTIFY_POS0 in sys/select.h, as clang complains about __gnu_inline__ in some cases. An issue which is already fixed with the shared macros. It was reported it: - https://gitlab.alpinelinux.org/alpine/aports/-/issues/18015 - https://gitlab.alpinelinux.org/alpine/aports/-/issues/18000 Co-Authored-By: Sertonix
2025-12-30Change __access into __fortify_access to fix potential conflictsjvoisin
2025-11-14Add `access` annotationsjvoisin
2025-11-10Add missing include in select.hq66
2025-10-31add initial clang supportDaniel Kolesa
Co-Authored-By: jvoisin <julien.voisin@dustri.org>
2025-10-31avoid __extension__ with clangDaniel Kolesa
It seems useless and triggers 'error: expected external declaration'
2025-10-31Make use of __builtin_dynamic_object_sizejvoisin
GCC and Clang provide __builtin_dynamic_object_size (see documentation: https://gcc.gnu.org/onlinedocs/gcc/Object-Size-Checking.html), so we should make use of it when its available.
2018-07-24Don't use __extension__ in C++ codeA. Wilcox
A few important notes: * __extension__ is a GNU C "alternate" keyword, not a C++ keyword.[1] * __extension__ is designed to work on "expressions"; it does work on #include_next in C mode, but it has no effect in C++ mode; the warning will still appear, if enabled, even with __extension__ preceding #include_next. This is because #include_next is not considered an expression in C++, so the compiler attaches __extension__ to the first expression of the header. All of this leads us to a build failure while building at least all Mozilla software. Moz has an alternate -isystem dir searched before /usr/include that overrides some headers, including <features.h>. The first statement in each of these headers is a #pragma, and since __extension__ is looking for an expression, and #pragma is a "null" expression, we end up with the following error: dist/system_wrappers/features.h:1:9: error: '#pragma' is not allowed here Since __extension__ has no effect on #include_next in C++ mode anyway, and since it can cause breakage, this commit omits __extension__ in C++ mode. [1]: https://gcc.gnu.org/onlinedocs/gcc-6.4.0/gcc/Alternate-Keywords.html
2016-09-10Bump copyright yearsin
2015-06-25Add __extension__ mark to include_next to silence -pedanticSteven Barth
Signed-off-by: Steven Barth <steven@midlink.org>
2015-06-04Use the __inline__ keyword instead of __inline to avoid breakageTrutz Behn
Newer compilers default to GNU11, a C11 dialect. Some software however is unprepared for this or has wrong compatibility checks. What happens is that some software will for compatibility with C89 #define inline before inclusion of a standard header, which is undefined behaviour in C99 and above (C99/C11 7.1.2/4), as inline is a keyword. If any libc headers that are then included via #include_next provide an __inline macro definition (current musl does this if C++ or C99 and above is detected) like the following #define __inline inline this results in any __inline token to be preprocessed away. This breaks use of __builtin_va_arg_pack() in our stdio.h at compile-time as it can only be used in always inlined functions. The function attributes __always_inline__ and __gnu_inline__ themselves require an inline specifier on the function to be applied.
2015-06-03Use namespace-safe macro, param and variable namesTrutz Behn
2015-05-21Fix return-type of fortified FD_CLR and FD_SETTrutz Behn
POSIX specifies them to have return-type void, not int.
2015-05-13Add LICENSE headersin
2015-05-13Add fortify_fn() helper in fortify-headers.hsin
2015-03-14Use __typeof__ to in part avoid replicating function typesTrutz Behn
2015-03-14Add __artificial__ to aid in debuggingsin
2015-03-13Restore C++ supportsin
2015-03-13Rework fortify implementation to use extern inlinesin
Overriding functions with macros is legal in C but a lot of software is not prepared for it. Use the extern inline method to achieve the same result.
2015-03-11Put include guards in the reserved namespaceTrutz Behn
fortify-headers is considered part of the implementation.
2015-03-11Ignore C++ for nowsin
It is not legal to override standard functions using macros in C++. We may have to revisit this in the future.
2015-03-11Add ifdef guards for C++ codesin
2015-02-28Add sendto() checksin
2015-02-24Add send() checksin
2015-02-24Remove compile time checkssin
These can produce false positives. Given that we support fortify source level 1 we shouldn't break valid code.
2015-02-22Remove header license commentssin
2015-02-04Remember to #undef __errordeclsin
Thanks zhasha for spotting this.
2015-02-04Style fixsin
2015-02-04Add recvfrom() checkssin
2015-01-30Add recv() checkssin
2015-01-30Use consistent naming conventionsin
2015-01-30Add FD_{CLR,SET} checkssin