glibc/setjmp
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
__longjmp.c
bsd-_setjmp.c
bsd-setjmp.c
bug269-setjmp.c
jmp_buf-macros.sym
jmp-unwind.c
jmpbug.c
longjmp.c
Makefile
setjmp.c
setjmp.h
sigjmp.c
tst-setjmp-check.c
tst-setjmp-fp.c
tst-setjmp-static.c
tst-setjmp.c
tst-sigsetjmp.c
Versions