From: Amaury Denoyelle <adenoyelle@haproxy.com>
Date: Fri, 23 Apr 2021 14:35:13 +0000 (+0200)
Subject: BUILD: compiler: do not use already defined __read_mostly on dragonfly
X-Git-Tag: v2.4-dev18~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d272b409d73f71b1a85dcc78b380a6188d194329;p=thirdparty%2Fhaproxy.git

BUILD: compiler: do not use already defined __read_mostly on dragonfly

DragonflyBSD already has an attribute __read_mostly which serves the
same purpose as the one in compiler.h.

No need to be backported as it was added in the current 2.4-dev.
---

diff --git a/include/haproxy/compiler.h b/include/haproxy/compiler.h
index 72557674c4..72d158b37e 100644
--- a/include/haproxy/compiler.h
+++ b/include/haproxy/compiler.h
@@ -89,7 +89,9 @@
 #endif // USE_OBSOLETE_LINKER
 
 /* use this attribute on a variable to move it to the read_mostly section */
+#if !defined(__DragonFly__)
 #define __read_mostly           HA_SECTION("read_mostly")
+#endif
 
 /* This allows gcc to know that some locations are never reached, for example
  * after a longjmp() in the Lua code, hence that some errors caught by such