From 090cafa0678333435486f2d70296311d20a2ed5d Mon Sep 17 00:00:00 2001
From: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Date: Thu, 6 Dec 2012 13:23:16 +0100
Subject: 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.
---
 src/shared/hashmap.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/shared/hashmap.c b/src/shared/hashmap.c
index dcfbb67228..a2c728d642 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) {
-- 
cgit v1.2.3-54-g00ecf