Use likely()/unlikely() macros to improve branch prediction.

[coloredstderr/coloredstderr.git] / configure.ac

diff --git a/configure.ac b/configure.ac
index f660e60ebdf7833167557a4b3fd8ec66132f65b3..ec5b65898d6d14f161557937e89f17406eb71732 100644 (file)
--- a/configure.ac
+++ b/configure.ac
@@ -32,6 +32,10 @@ dnl Used by test suite.
 AC_PROG_SED
 AC_PROG_EGREP
 
+if test "x$GCC" = xyes; then
+    CFLAGS="-Wall -Wextra -Wconversion $CFLAGS"
+fi
+
 AC_CHECK_HEADERS([fcntl.h error.h])
 
 AC_TYPE_PID_T
@@ -43,6 +47,14 @@ AC_C_INLINE
 AC_FUNC_FORK
 AC_CHECK_FUNCS([dup2 memmove setenv strdup])
 
+dnl Thanks to gperftools' configure.ac (https://code.google.com/p/gperftools).
+AC_MSG_CHECKING([for __builtin_expect])
+AC_LINK_IFELSE([AC_LANG_PROGRAM([],[return __builtin_expect(main != 0, 1)])],
+               [AC_DEFINE([HAVE___BUILTIN_EXPECT], 1,
+                          [Define to 1 if the compiler supports __builtin_expect().])
+                AC_MSG_RESULT([yes])],
+               [AC_MSG_RESULT([no])])
+
 AC_SEARCH_LIBS([dlsym], [dl], [], [AC_MSG_ERROR([dlsym() is required])])
 
 AC_ARG_ENABLE([debug],