aboutsummaryrefslogtreecommitdiff
path: root/perf.c
diff options
context:
space:
mode:
authorDavid Sommerseth <dazo@users.sourceforge.net>2010-11-15 08:48:57 +0100
committerDavid Sommerseth <dazo@users.sourceforge.net>2010-11-18 18:54:49 +0100
commiteabb8eed0bc3b2b16722eeb38d8000eda35668a7 (patch)
tree0ba8f9cf032aadde50924015ec0ba6b896dd11de /perf.c
parentUse stricter snprintf() formatting in socks_username_password_auth() (v3) (diff)
downloadopenvpn-eabb8eed0bc3b2b16722eeb38d8000eda35668a7.tar.xz
Fix compiler warnings about not used dummy() functions
It has been reported that the Microsoft Visual C compiler complains if a .c file do not contain any compilable code, which can happen if the code has been #ifdef'ed out. To avoid this, these #ifdef sections have a #else section which adds a static dummy() function which does nothing. On the other hand, the GNU C compiler complains about unused functions when it discovers this situation. This patch tries to only add these dummy() functions if the Microsoft Visual C compiler is detected, via the _MSC_VER macro. Signed-off-by: David Sommerseth <dazo@users.sourceforge.net> Acked-by: Peter Stuge <peter@stuge.se>
Diffstat (limited to '')
-rw-r--r--perf.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/perf.c b/perf.c
index a149c07..67ea958 100644
--- a/perf.c
+++ b/perf.c
@@ -287,5 +287,7 @@ perf_print_state (int lev)
}
#else
+#ifdef _MSC_VER /* Dummy function needed to avoid empty file compiler warning in Microsoft VC */
static void dummy(void) {}
#endif
+#endif