From: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Date: Thu, 6 Dec 2012 12:23:16 +0000 (+0100)
Subject: build-sys: use VALGRIND not __OPTIMIZE__ as condition for valgrind compat
X-Git-Tag: v197~34
X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=commitdiff_plain;h=090cafa0678333435486f2d70296311d20a2ed5d;ds=sidebyside

build-sys: use VALGRIND not __OPTIMIZE__ as condition for valgrind compat

Actually, one might want to run valgrind even on optimized code.
Now the same check is used in the jenkins hash functions and
hashtable.
---

diff --git a/src/shared/hashmap.c b/src/shared/hashmap.c
index dcfbb6722..a2c728d64 100644
--- a/src/shared/hashmap.c
+++ b/src/shared/hashmap.c
@@ -103,7 +103,7 @@ static void deallocate_tile(void **first_tile, void *p) {
         *first_tile = p;
 }
 
-#ifndef __OPTIMIZE__
+#ifdef VALGRIND
 
 static void drop_pool(struct pool *p) {
         while (p) {