From ce2248ab91b2ea09a378f85012f251f31ac65e31 Mon Sep 17 00:00:00 2001 From: Florian Weimer Date: Thu, 9 Dec 2021 09:49:32 +0100 Subject: nptl: Introduce for THREAD_* accessors These are common between most architectures. Only the x86 targets are outliers. Reviewed-by: Szabolcs Nagy --- sysdeps/m68k/nptl/tls.h | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) (limited to 'sysdeps/m68k/nptl') diff --git a/sysdeps/m68k/nptl/tls.h b/sysdeps/m68k/nptl/tls.h index 34906b1c13..257af6bddc 100644 --- a/sysdeps/m68k/nptl/tls.h +++ b/sysdeps/m68k/nptl/tls.h @@ -117,15 +117,7 @@ extern void * __m68k_read_tp (void); # define DB_THREAD_SELF \ CONST_THREAD_AREA (32, TLS_TCB_OFFSET + TLS_PRE_TCB_SIZE) -/* Access to data in the thread descriptor is easy. */ -# define THREAD_GETMEM(descr, member) \ - descr->member -# define THREAD_GETMEM_NC(descr, member, idx) \ - descr->member[idx] -# define THREAD_SETMEM(descr, member, value) \ - descr->member = (value) -# define THREAD_SETMEM_NC(descr, member, idx, value) \ - descr->member[idx] = (value) +# include /* l_tls_offset == 0 is perfectly valid on M68K, so we have to use some different value to mean unset l_tls_offset. */ -- cgit 1.4.1