aboutsummaryrefslogtreecommitdiff
path: root/rt/tst-aio4.c
diff options
context:
space:
mode:
authorNick Alcock <nick.alcock@oracle.com>2016-12-26 10:08:54 +0100
committerFlorian Weimer <fweimer@redhat.com>2016-12-26 10:10:58 +0100
commit66a704c43cfec810fea67a6959f2d1c94f4d594f (patch)
tree174dece4f1f3b73874398c029f8aa96911632e9d /rt/tst-aio4.c
parentbc174f20b83d19167ecac14ce0762eddbe47cc64 (diff)
downloadglibc-66a704c43cfec810fea67a6959f2d1c94f4d594f.tar
glibc-66a704c43cfec810fea67a6959f2d1c94f4d594f.tar.gz
glibc-66a704c43cfec810fea67a6959f2d1c94f4d594f.tar.bz2
glibc-66a704c43cfec810fea67a6959f2d1c94f4d594f.zip
Work even with compilers which enable -fstack-protector by default [BZ #7065]
With all the machinery we just added, we can easily arrange to work even when the compiler passes in -fstack-protector automatically: all the necessary bits of glibc are always compiled with -fno-stack-protector now. So tear out the check in configure, and add appropriate calls to -fno-stack-protector in tests that need them (largely those that use -nostdlib), since we don't yet have a __stack_chk_fail that those tests can rely upon. (GCC often provides one, but we cannot rely on this, especially not when bootstrapping.) When stack protection is disabled, explicitly pass -fno-stack-protector to everything, to stop a compiler hacked to enable it from inserting calls to __stack_chk_fail via the PLT in every object file.
Diffstat (limited to 'rt/tst-aio4.c')
0 files changed, 0 insertions, 0 deletions