Disable -Waddress for part of nptl/tst-mutex1.c
Commit Message
On Tue, 2 Dec 2014, Roland McGrath wrote:
> The ATTR_NULL approach seems far cleaner to me. Why disable warnings when
> a code cleanup suffices?
Here is a patch using ATTR_NULL. Tested for x86_64.
2014-12-02 Joseph Myers <joseph@codesourcery.com>
* nptl/tst-mutex1.c: Include <stdbool.h>.
[!ATTR] (ATTR_NULL): New macro.
(do_test): Test !ATTR_NULL instead of ATTR != NULL.
* nptl/tst-mutexpi1.c (ATTR_NULL): New macro.
* nptl/tst-mutexpp1.c (ATTR_NULL): New macro.
Comments
@@ -19,10 +19,12 @@
#include <pthread.h>
#include <stdio.h>
#include <errno.h>
+#include <stdbool.h>
#ifndef ATTR
# define ATTR NULL
+# define ATTR_NULL true
#endif
@@ -32,7 +34,7 @@ do_test (void)
pthread_mutex_t m;
int e = pthread_mutex_init (&m, ATTR);
- if (ATTR != NULL && e == ENOTSUP)
+ if (!ATTR_NULL && e == ENOTSUP)
{
puts ("cannot support selected type of mutexes");
return 0;
@@ -43,7 +45,7 @@ do_test (void)
return 1;
}
- if (ATTR != NULL && pthread_mutexattr_destroy (ATTR) != 0)
+ if (!ATTR_NULL && pthread_mutexattr_destroy (ATTR) != 0)
{
puts ("mutexattr_destroy failed");
return 1;
@@ -24,4 +24,5 @@ prepare (void)
#define ATTR &a
+#define ATTR_NULL false
#include "tst-mutex1.c"
@@ -42,4 +42,5 @@ do_test_wrapper (void)
#define TEST_FUNCTION do_test_wrapper ()
#define ATTR &a
+#define ATTR_NULL false
#include "tst-mutex1.c"