| #
032acb9e |
| 05-Sep-2020 |
mrg <mrg@NetBSD.org> |
make the 2nd argument to __memmove_chk() const
|
| #
a2388441 |
| 29-Nov-2014 |
pooka <pooka@NetBSD.org> |
Create the stpncpy() inline only when GCC>=4.8 || clang
Mirrors the stpncpy() wrapper macro and avoids the following: warning: implicit declaration of function ‘__builtin___stpncpy_chk’
|
| #
366b2dd2 |
| 25-Apr-2014 |
pooka <pooka@NetBSD.org> |
Apparently clang pretends to be gcc 4.2 but is secretly much awesomer than gcc 4.2, so enable the stpncpy() wrapper also for clang.
|
| #
232a041b |
| 24-Apr-2014 |
pooka <pooka@NetBSD.org> |
Wrap stpncpy() iff GNUC_PREREQ(4,8). Fixes USE_SSP=yes builds with gcc 4.5.
|
| #
73447a65 |
| 06-Apr-2014 |
christos <christos@NetBSD.org> |
add stpncpy()
|
| #
53e3f1af |
| 07-Nov-2013 |
christos <christos@NetBSD.org> |
gcc-4.8.1 is has a builtin stpncpy, but is missing the __builtin_ ssp equivalent. go figure.
|
| #
fb23e6a8 |
| 07-Nov-2013 |
tron <tron@NetBSD.org> |
Revert my last change. I'm not convinced it is correct and while it seems to fix some build problems it might cause others.
|
| #
24f67c87 |
| 06-Nov-2013 |
tron <tron@NetBSD.org> |
Add missing declarations for SSP versions of stpcpy(3) and stpncpy(3).
|
| #
c15ffc14 |
| 06-Nov-2013 |
christos <christos@NetBSD.org> |
add stp{,n}cpy
|
| #
37a2d02f |
| 22-Jul-2012 |
joerg <joerg@NetBSD.org> |
Always provide *_chk prototypes. Fixes DBG=-g build of libc.
|
| #
750e2bab |
| 17-Nov-2009 |
drochner <drochner@NetBSD.org> |
add some prototypes for checked string functions
|
| #
ce099b40 |
| 28-Apr-2008 |
martin <martin@NetBSD.org> |
Remove clause 3 and 4 from TNF licenses
|
| #
dc99372b |
| 30-May-2007 |
tls <tls@NetBSD.org> |
Match usage of FORTIFY_SOURCE on other platforms by not requiring special include path: the normal header files now include the "SSP" ones (which one should note are not really named right: SSP and F
Match usage of FORTIFY_SOURCE on other platforms by not requiring special include path: the normal header files now include the "SSP" ones (which one should note are not really named right: SSP and FORTIFY_SOURCE are independent features).
Disable USE_SSP on targets where the compiler doesn't support it at all (mips, alpha) or it's known broken (sh3). But enable FORTIFY_SOURCE, without SSP, on those platforms -- tested on mipsel.
show more ...
|
| #
2368dc66 |
| 30-May-2007 |
tls <tls@NetBSD.org> |
Move FORTIFY_SOURCE implementation from the somewhat ill-named "libssp" (what other systems keep in libssp, we already have in libc) into libc to match what other systems with FORTIFY_SOURCE do. Goo
Move FORTIFY_SOURCE implementation from the somewhat ill-named "libssp" (what other systems keep in libssp, we already have in libc) into libc to match what other systems with FORTIFY_SOURCE do. Goodbye, libssp dependency in libraries and executables. Discussed with christos and mrg; Christos will merge the headers to get us the rest of the way to a FORTIFY_SOURCE implementation that works as others' code expects.
show more ...
|