From 2d18717fb808441e3214cc50409fe358ea67497c Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date: Sat, 12 Aug 2023 19:58:17 +0200 Subject: [PATCH] BUILD: pools: fix build error on clang with inline vs forceinline clang is more picky than gcc regarding duplicate "inline". The functions declared with "forceinline" don't need to have "inline" since it's already in the macro. --- src/pool.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pool.c b/src/pool.c index 7cb71d00fc..341c3b4d86 100644 --- a/src/pool.c +++ b/src/pool.c @@ -115,7 +115,7 @@ static int(*_malloc_trim)(size_t) = NULL; * allocated on one thread and released on another one. Thus only the * pointer is usable. */ -static inline forceinline unsigned int pool_pbucket(const void *ptr) +static forceinline unsigned int pool_pbucket(const void *ptr) { return ptr_hash(ptr, CONFIG_HAP_POOL_BUCKETS_BITS); } @@ -123,7 +123,7 @@ static inline forceinline unsigned int pool_pbucket(const void *ptr) /* returns the pool hash bucket to use for the current thread. This should only * be used when no pointer is available (e.g. count alloc failures). */ -static inline forceinline unsigned int pool_tbucket(void) +static forceinline unsigned int pool_tbucket(void) { return tid % CONFIG_HAP_POOL_BUCKETS; } -- 2.47.3