fortify-headers/include/sys/select.h, branch 0.7Standalone portable header-based implementation of FORTIFY_SOURCE=3
http://git.dustri.org/fortify-headers/atom?h=0.72015-06-25T09:18:26ZAdd __extension__ mark to include_next to silence -pedantic2015-06-25T09:18:26ZSteven Barth2015-06-24T18:13:37Zurn:sha1:7fd984fcb532be01f68cddc194c09a7ca10c1ea6
Signed-off-by: Steven Barth <steven@midlink.org>
Use the __inline__ keyword instead of __inline to avoid breakage2015-06-04T17:52:50ZTrutz Behn2015-06-04T13:01:37Zurn:sha1:4cdac9cbdaa01f884e0e8b3f947b7f0cb1170729
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.
Use namespace-safe macro, param and variable names2015-06-03T17:55:35ZTrutz Behn2015-06-03T17:27:01Zurn:sha1:1cd5461a5375207602f2cbdfd9a50a9b751cb7c8Fix return-type of fortified FD_CLR and FD_SET2015-05-21T09:10:17ZTrutz Behn2015-05-20T20:09:46Zurn:sha1:720c4f7414c3c3d980de8e6ddbc0f608d3e9050d
POSIX specifies them to have return-type void, not int.
Add LICENSE header2015-05-13T11:15:36Zsin2015-05-13T11:15:36Zurn:sha1:07adb509146e4185b9b7587baad26cdfb766c67eAdd __artificial__ to aid in debugging2015-03-14T09:38:22Zsin2015-03-14T09:38:11Zurn:sha1:37eb2c9c1d71c2ff21605ecaf46cdd926244d361Restore C++ support2015-03-13T23:09:15Zsin2015-03-13T23:09:15Zurn:sha1:d12254166a55d17932ea4143fbd50fb52539ff8bRework fortify implementation to use extern inline2015-03-13T11:00:46Zsin2015-03-13T11:00:46Zurn:sha1:9f8c543dc81f0c4239acae6713f5414eb7dc681d
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.
Put include guards in the reserved namespace2015-03-11T21:33:01ZTrutz Behn2015-03-11T18:55:51Zurn:sha1:b211796d68c4a6b56f999534627791f3576b6135
fortify-headers is considered part of the implementation.
Ignore C++ for now2015-03-11T11:18:31Zsin2015-03-11T11:18:31Zurn:sha1:14af218559243c1e16cf871e1823f1a5d8cece9f
It is not legal to override standard functions using macros in C++.
We may have to revisit this in the future.