glibc/sysdeps/unix/sysv/linux/s390/s390-64
Carlos O'Donell 47dd3543d3 Bug 20198: quick_exit should not call destructors.
In C++11 18.5.12 says "Objects shall not be destroyed as a
result of calling quick_exit." In C11 quick_exit is silent
about thread object destruction. Therefore to make glibc
C++ compliant we do not call any thread local destructors.
A new regression test verifies the fix.

I will note that C++11 18.5.3 makes it clear that C++
defines additional requirements for _Exit() to prevent it
from executing destructors.

Given that the point of _Exit() is to terminate the process
immediately it makes sense the C and C++ should line up
and avoid calling destructors.

No failures. New regtest passes.
2016-06-06 21:40:25 -04:00
..
Implies
Makefile
Versions network: recvmsg and sendmsg standard compliance (BZ#16919) 2016-05-25 17:39:01 -03:00
____longjmp_chk.c
__makecontext_ret.S
c++-types.data
clone.S
configure
configure.ac
dl-cache.h
getcontext.S
kernel_stat.h
ld.abilist
libBrokenLocale.abilist
libc.abilist Bug 20198: quick_exit should not call destructors. 2016-06-06 21:40:25 -04:00
libcrypt.abilist
libdl.abilist
libm.abilist
libnsl.abilist
libpthread.abilist
libresolv.abilist
librt.abilist
libthread_db.abilist
libutil.abilist
makecontext.c
mmap.S
profil-counter.h
register-dump.h
setcontext.S
shlib-versions
sigaction.c
sigpending.c
sigprocmask.c
swapcontext.S
syscall.S
syscalls.list
sysdep-cancel.h
sysdep.S
sysdep.h
timer_create.c
timer_delete.c
timer_getoverr.c
timer_gettime.c
timer_settime.c
vfork.S