fortify-headers/include/sys, branch 2.0

Add hardening for select()

2023-11-16T15:42:41Z

This is unlikely to be used, since fd_set is usually manipulated by macros, but it doesn't hurt to add a simple comparison.

Add support for FD_ISSET

2023-11-01T20:55:04Z

Clean up some includes

2023-08-22T18:08:52Z

- Remove a superfluous `#if defined(__has_builtin)` since it's already accounted for in include/fortify-headers.h - Replace `_FORTIFY_FD_POS0` with the already existing `_FORTIFY_POS0` - Factorise some duplicate code into a macro

Harden umask

2023-08-21T15:48:29Z

Add access annotations to sys/socket.h

2023-07-05T13:48:14Z

add initial clang support

2023-06-25T16:26:45Z

avoid extension with clang

2023-06-25T16:13:11Z

It seems useless and triggers 'error: expected external declaration'

Make use of __builtin_dynamic_object_size

2023-04-13T21:48:57Z

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.

Don't use extension in C++ code

2018-07-24T10:00:30Z

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 . 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

Bump copyright year

2016-09-10T11:54:17Z