From 22ce18019f83b1f9826c32aa2ee56dc0df3fbd49 Mon Sep 17 00:00:00 2001 From: "H.J. Lu" Date: Sun, 2 Aug 2015 22:27:47 -0700 Subject: Don't run tst-getpid2 with LD_BIND_NOW=1 Since _dl_x86_64_save_sse and _dl_x86_64_restore_sse are removed now, we don't need to run tst-getpid2 with LD_BIND_NOW=1. * nptl/Makefile (tst-getpid2-ENV): Removed. --- nptl/Makefile | 5 ----- 1 file changed, 5 deletions(-) diff --git a/nptl/Makefile b/nptl/Makefile index 43d85103f8..1e8f566c8f 100644 --- a/nptl/Makefile +++ b/nptl/Makefile @@ -463,11 +463,6 @@ tst-cancel7-ARGS = --command "exec $(host-test-program-cmd)" tst-cancelx7-ARGS = $(tst-cancel7-ARGS) tst-umask1-ARGS = $(objpfx)tst-umask1.temp -# In this test, we create a CLONE_VM "thread" that shares TLS storage -# with the original thread. Both threads then race in ld.so with lazy PLT -# resolution. Avoid this race by disabling lazy binding. BZ #11214. -tst-getpid2-ENV = LD_BIND_NOW=1 - $(objpfx)tst-atfork2: $(libdl) $(shared-thread-library) LDFLAGS-tst-atfork2 = -rdynamic tst-atfork2-ENV = MALLOC_TRACE=$(objpfx)tst-atfork2.mtrace -- cgit 1.4.1