From c8e8ac42abb9225c3abfac036340548cfaaa0e92 Mon Sep 17 00:00:00 2001 From: Chris Robinson Date: Sun, 24 Mar 2019 14:02:06 -0700 Subject: Use false instead of 0 for a boolean --- common/opthelpers.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'common') diff --git a/common/opthelpers.h b/common/opthelpers.h index b496942c..c83229f5 100644 --- a/common/opthelpers.h +++ b/common/opthelpers.h @@ -12,9 +12,9 @@ * required to be true, but it can result in more optimal code for the true * path at the expense of a less optimal false path. */ -#define LIKELY(x) __builtin_expect(!!(x), !0) +#define LIKELY(x) __builtin_expect(!!(x), !false) /* The opposite of LIKELY, optimizing the case where the condition is false. */ -#define UNLIKELY(x) __builtin_expect(!!(x), 0) +#define UNLIKELY(x) __builtin_expect(!!(x), false) /* Unlike LIKELY, ASSUME requires the condition to be true or else it invokes * undefined behavior. It's essentially an assert without actually checking the * condition at run-time, allowing for stronger optimizations than LIKELY. -- cgit v1.2.3