about summary refs log tree commit diff
path: root/support/xpthread_mutexattr_destroy.c
diff options
context:
space:
mode:
authorSergey Bugaev <bugaevc@gmail.com>2021-09-07 16:33:21 +0300
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2021-09-15 01:29:23 +0200
commit520a5887057c328c99304d6947453eb06351f5fd (patch)
tree46c68436cf80c498588a56184191a3e9afcb5e94 /support/xpthread_mutexattr_destroy.c
parent3561106278cddd2f007bd27fd4c3e90caaf14b43 (diff)
downloadglibc-520a5887057c328c99304d6947453eb06351f5fd.tar.gz
glibc-520a5887057c328c99304d6947453eb06351f5fd.tar.xz
glibc-520a5887057c328c99304d6947453eb06351f5fd.zip
elf: Replace most uses of THREAD_GSCOPE_IN_TCB
While originally this definition was indeed used to distinguish between
the cases where the GSCOPE flag was stored in TCB or not, it has since
become used as a general way to distinguish between HTL and NPTL.

THREAD_GSCOPE_IN_TCB will be removed in the following commits, as HTL,
which currently is the only port that does not put the flag into TCB,
will get ported to put the GSCOPE flag into the TCB as well. To prepare
for that change, migrate all code that wants to distinguish between HTL
and NPTL to use PTHREAD_IN_LIBC instead, which is a better choice since
the distinction mostly has to do with whether libc has access to the
list of thread structures and therefore can initialize thread-local
storage.

The parts of code that actually depend on whether the GSCOPE flag is in
TCB are left unchanged.

Signed-off-by: Sergey Bugaev <bugaevc@gmail.com>
Message-Id: <20210907133325.255690-2-bugaevc@gmail.com>
Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
Diffstat (limited to 'support/xpthread_mutexattr_destroy.c')
0 files changed, 0 insertions, 0 deletions