fortify-headers/include/string.h, branch annotations

Add `access` annotations

2025-11-14T12:55:31Z

add initial clang support

2025-10-31T21:16:21Z

Co-Authored-By: jvoisin

avoid extension with clang

2025-10-31T21:16:21Z

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

Make use of __builtin_dynamic_object_size

2025-10-31T21:16:21Z

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.

Make use of builtins whenever possible

2019-02-25T13:17:08Z

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

Fix stpncpy() check

2015-07-15T16:02:27Z

Do not crash unless the overflow would happen.

Add extension mark to include_next to silence -pedantic

2015-06-25T09:18:26Z

Signed-off-by: Steven Barth

Use namespace-safe macro, param and variable names

2015-06-03T17:55:35Z

fortify-headers/include/string.h, branch annotations

Add `access` annotations

add initial clang support

avoid __extension__ with clang

Make use of __builtin_dynamic_object_size

Make use of builtins whenever possible

Don't use __extension__ in C++ code

Bump copyright year

Fix stpncpy() check

Add __extension__ mark to include_next to silence -pedantic

Use namespace-safe macro, param and variable names

avoid extension with clang

Don't use extension in C++ code

Add extension mark to include_next to silence -pedantic