[PATCH 7/7] Don't run tst-getpid2 with LD_BIND_NOW=1

[H.J. Lu]

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.

OK for master?

H.J.
---
	* sysdeps/unix/sysv/linux/Makefile (tst-getpid2-ENV): Removed.
---
 sysdeps/unix/sysv/linux/Makefile | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/sysdeps/unix/sysv/linux/Makefile b/sysdeps/unix/sysv/linux/Makefile
index bfbabd4..2c67a66 100644
--- a/sysdeps/unix/sysv/linux/Makefile
+++ b/sysdeps/unix/sysv/linux/Makefile
@@ -193,9 +193,4 @@ endif
 
 ifeq ($(subdir),nptl)
 tests += tst-setgetname tst-align-clone tst-getpid1 tst-getpid2
-
-# 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
 endif
-- 
2.4.3