fortify-headers/include/sys/socket.h, branch 2.1Standalone portable header-based implementation of FORTIFY_SOURCE=3
http://git.dustri.org/fortify-headers/atom?h=2.12023-12-15T22:50:43ZRename some macros to be more namespace-friendly2023-12-15T22:50:43Zq662023-12-15T22:48:58Zurn:sha1:a018052d410126f94c2602b208b099839d333b05Remove superfluous includes2023-12-15T20:41:08Zjvoisin2023-12-15T15:08:12Zurn:sha1:57a3e9c1c7507b5ce56122429cc3649009a4ecc7
This should fix #32
Add access annotations to sys/socket.h2023-07-05T13:48:14Zjvoisin2023-07-05T13:48:14Zurn:sha1:62199030394acd30ab44bc21af7078ae993fd149add initial clang support2023-06-25T16:26:45ZDaniel Kolesa2022-10-25T22:30:00Zurn:sha1:fe149628eaae9748be08815d726cc56e8e492c73avoid __extension__ with clang2023-06-25T16:13:11ZDaniel Kolesa2022-11-01T19:14:54Zurn:sha1:adae76af26e498af6c3004a52a4b1de2c6fd91c3
It seems useless and triggers 'error: expected external declaration'
Make use of __builtin_dynamic_object_size2023-04-13T21:48:57Zjvoisin2023-03-18T13:01:02Zurn:sha1:3e6704d0be707487d7a9dccfdc75203c7261e11b
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++ code2018-07-24T10:00:30ZA. Wilcox2018-06-23T22:57:48Zurn:sha1:a9ffac8596b094da8563aa5dd5d81c946670afe5
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
Bump copyright year2016-09-10T11:54:17Zsin2016-09-10T11:54:06Zurn:sha1:2bc423c355a992fea2f95724235898218575c95eAdd __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 namespace-safe macro, param and variable names2015-06-03T17:55:35ZTrutz Behn2015-06-03T17:27:01Zurn:sha1:1cd5461a5375207602f2cbdfd9a50a9b751cb7c8