Frédéric Bérat 20c894d21e Exclude routines from fortification ... Since the _FORTIFY_SOURCE feature uses some routines of Glibc, they need to be excluded from the fortification. On top of that: - some tests explicitly verify that some level of fortification works appropriately, we therefore shouldn't modify the level set for them. - some objects need to be build with optimization disabled, which prevents _FORTIFY_SOURCE to be used for them. Assembler files that implement architecture specific versions of the fortified routines were not excluded from _FORTIFY_SOURCE as there is no C header included that would impact their behavior. Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>		2023-07-05 16:59:48 +02:00
..
bits
sys	Fix all the remaining misspellings -- BZ 25337	2023-06-02 01:39:48 +00:00
accept4.c
accept.c
bind.c
connect.c
getpeername.c
getsockname.c
getsockopt.c
isfdtype.c
listen.c
Makefile	Exclude routines from fortification	2023-07-05 16:59:48 +02:00
opensock.c
recv.c
recvfrom.c
recvmmsg.c
recvmsg.c
sa_len.c
send.c
sendmmsg.c
sendmsg.c
sendto.c
setsockopt.c
shutdown.c
sockaddr_un_set.c
sockatmark.c
socket.c
socketpair.c
tst-accept4.c
tst-cmsg_cloexec.c
tst-cmsghdr-skeleton.c
tst-cmsghdr.c
tst-sockaddr_un_set.c
tst-sockopt-time64.c
tst-sockopt.c
Versions