[glibc/fw/syscall-cleanups] Linux: set_tid_address syscall number is always available

[glibc/fw/syscall-cleanups] Linux: set_tid_address syscall number is always available

[Florian Weimer]

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c108ce5c715d767bc13e181ddc9f944e7aa3b962

commit c108ce5c715d767bc13e181ddc9f944e7aa3b962
Author: Florian Weimer <fweimer@redhat.com>
Date:   Sun Feb 9 16:30:28 2020 +0100

    Linux: set_tid_address syscall number is always available
    
    Due to the built-in tables, __NR_set_tid_address is always defined.

Diff:
---
 sysdeps/unix/sysv/linux/nscd_setup_thread.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/sysdeps/unix/sysv/linux/nscd_setup_thread.c b/sysdeps/unix/sysv/linux/nscd_setup_thread.c
index 6e14918..a49676f 100644
--- a/sysdeps/unix/sysv/linux/nscd_setup_thread.c
+++ b/sysdeps/unix/sysv/linux/nscd_setup_thread.c
@@ -25,7 +25,6 @@
 int
 setup_thread (struct database_dyn *db)
 {
-#ifdef __NR_set_tid_address
   /* Only supported when NPTL is used.  */
   char buf[100];
   if (confstr (_CS_GNU_LIBPTHREAD_VERSION, buf, sizeof (buf)) >= sizeof (buf)
@@ -43,7 +42,6 @@ setup_thread (struct database_dyn *db)
        So, set the field to a nonzero value which indicates that nscd
        is certainly running and clients can skip the test.  */
     return db->head->nscd_certainly_running = 1;
-#endif
 
   return 0;
 }