diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2012-12-06 13:23:16 +0100 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2013-01-06 13:52:47 -0500 |
| commit | 090cafa0678333435486f2d70296311d20a2ed5d (patch) | |
| tree | a79dfcd767796de0b13d0af56210e4784c335627 | |
| parent | 24fdc2300451372bd098a7cab39f3a417d46605b (diff) | |
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.
| -rw-r--r-- | src/shared/hashmap.c | 2 |
1 files changed, 1 insertions, 1 deletions
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) { |