summaryrefslogtreecommitdiff
path: root/include/string.h (follow)
AgeCommit message (Collapse)Author
2025-12-30Change __warning_if into __fortify_warning_if to fix potential conflicts3.0.1jvoisin
2025-12-30Change __access into __fortify_access to fix potential conflictsjvoisin
2025-11-14Add __diagnose_if annotations3.0jvoisin
2025-11-14Add `access` annotationsjvoisin
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.
2019-02-25Make use of builtins whenever possiblesin
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-07-15Fix stpncpy() checksin
Do not crash unless the overflow would happen.
2015-06-25Add __extension__ mark to include_next to silence -pedanticSteven Barth
Signed-off-by: Steven Barth <steven@midlink.org>
2015-06-03Use namespace-safe macro, param and variable namesTrutz Behn
2015-05-13Add LICENSE headersin
2015-05-13Add fortify_fn() helper in fortify-headers.hsin
2015-04-08Check for out of bound reads for memcpy, memmove and mempcpy()sin
2015-03-15Hide stpcpy() and stpncpy() under feature test macrossin
2015-03-14Use __typeof__ to in part avoid replicating function typesTrutz Behn
2015-03-14Explicitly cast pointers to satisfy C++ codesin
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-11Revert "Add explicit casts to satisfy C++ code"sin
This reverts commit 1fbf7a3a5e9c02cf992848002cfb88c3c7cc0212.
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-03-11Add explicit casts to satisfy C++ codesin
2015-03-11Revert "Fix invalid conversion in C++ code"sin
This reverts commit 4b4dfea25d660a8a27e95ea531686001246b3d1e.
2015-03-11Fix invalid conversion in C++ codesin
/usr/include/fortify/string.h: In function 'void* __fortify_memcpy(void*, const void*, size_t)': /usr/include/fortify/string.h:13:12: error: invalid conversion from 'void*' to 'char*' [-fpermissive] /usr/include/fortify/string.h:14:18: error: invalid conversion from 'const void*' to 'const char*' [-fpermissive] Since we are relying on GCC anyway, assume void * arithmetic is OK.
2015-03-10Fix strncat() and strncpy() mappingssin
Thanks zhasha.
2015-02-25Clarify comment a bitsin
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-01-30Remove __restrictsin
2015-01-29Fix typosin
2015-01-29Allow dest == src in memcpy()sin
memcpy() needs to accept dest == src for gcc. struct foo a, b; a = a; might be implemented using memcpy().
2015-01-29Add compile-time checks as wellsin
2015-01-29Add license infosin
2015-01-29Trap if memcpy() pointers are overlappingsin
Maybe this should only be done if _FORTIFY_SOURCE > 1.
2015-01-28Use BSD-style func defssin
2015-01-28Use #ifdef instead of #if definedsin
2015-01-28Add mempcpy() checkssin
2015-01-28Simplify checkssin
Do not perform checks only when `n' is constant, most of the time it is not. The bos == (size_t)-1 check is redundant because n > bos with bos == -1 will always be false.
2015-01-28Remove trailing semicolonsin
2015-01-28Add stpncpy()sin
2015-01-28Add stpcpy()sin
2015-01-28Move defines to the bottomsin
This allows us to re-use the functions internally.
2015-01-28Merge __foo_chk() into __fortify_foo()sin