Add runtime check if mutex will be elided in tst-mutex8 testcases.

An elided mutex don't fail destroy. Elision was disabled for the
test nptl/tst-mutex8 in nptl/Makefile. Thus we can run tests which
destroy a locked mutex.

As elision is only disabled for tst-mutex8, the variants
tst-mutex8-static, tst-mutexpi8 and tst-mutexpi8-static are still
failing if lock elision is enabled.

This patch adds a runtime check, if the checked type of mutex will
be elided. This check is using TUNABLE_GET_FULL to determine if
elision is enabled via the tunables framework.
The pthread_mutex_destroy tests are only run if we dont't assume an
elided mutex.

This way, we can run the whole glibc testsuite with or without enabled
lock elision.

ChangeLog:

	* nptl/Makefile (tst-mutex8-ENV): Delete.
	* nptl/tst-mutex8.c (check_type):
	Add runtime check if mutex will be elided.

1 files changed, 6 insertions, 0 deletions

diff --git a/ChangeLog b/ChangeLog
index c5696dbe36..50ba118f79 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2018-02-16  Stefan Liebler  <stli@linux.vnet.ibm.com>
+
+	* nptl/Makefile (tst-mutex8-ENV): Delete.
+	* nptl/tst-mutex8.c (check_type):
+	Add runtime check if mutex will be elided.
+
 2018-02-15  Joseph Myers  <joseph@codesourcery.com>
 
 	[BZ #20980]