summaryrefslogtreecommitdiff
path: root/sequencer.c
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2016-11-09 03:57:28 (GMT)
committerJeff King <peff@peff.net>2016-11-09 03:59:24 (GMT)
commit2ae38f2a65abae910ff7ad62861414d4333d01fc (patch)
tree23da3c77d27543b677424a4336e07b413c94a8e1 /sequencer.c
parent791eb8708f7a98c9f3924b1810c20a9c7dd4c767 (diff)
downloadgit-2ae38f2a65abae910ff7ad62861414d4333d01fc.zip
git-2ae38f2a65abae910ff7ad62861414d4333d01fc.tar.gz
git-2ae38f2a65abae910ff7ad62861414d4333d01fc.tar.bz2
sequencer: silence -Wtautological-constant-out-of-range-compare
When clang compiles sequencer.c, it complains: sequencer.c:632:14: warning: comparison of constant 2 with expression of type 'const enum todo_command' is always true [-Wtautological-constant-out-of-range-compare] if (command < ARRAY_SIZE(todo_command_strings)) This is because "command" is an enum that may only have two values (0 and 1) and the array in question has two elements. As it turns out, clang is actually wrong here, at least according to its own bug tracker: https://llvm.org/bugs/show_bug.cgi?id=16154 But it's still worth working around this, as the warning is present with -Wall, meaning we fail compilation with "make DEVELOPER=1". Casting the enum to size_t sufficiently unconfuses clang. As a bonus, it also catches any possible out-of-bounds access if the enum takes on a negative value (which shouldn't happen either, but again, this is a defensive check). Signed-off-by: Jeff King <peff@peff.net>
Diffstat (limited to 'sequencer.c')
-rw-r--r--sequencer.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sequencer.c b/sequencer.c
index a61fe76..fae2bbd 100644
--- a/sequencer.c
+++ b/sequencer.c
@@ -629,7 +629,7 @@ static const char *todo_command_strings[] = {
static const char *command_to_string(const enum todo_command command)
{
- if (command < ARRAY_SIZE(todo_command_strings))
+ if ((size_t)command < ARRAY_SIZE(todo_command_strings))
return todo_command_strings[command];
die("Unknown command: %d", command);
}