From 4df5e91867498f7c6ee4bf5a464a5c24dc89034b Mon Sep 17 00:00:00 2001 From: Jeff King Date: Tue, 30 Aug 2016 23:41:22 -0400 Subject: error_errno: use constant return similar to error() Commit e208f9c (make error()'s constant return value more visible, 2012-12-15) introduced some macro trickery to make the constant return from error() more visible to callers, which in turn can help gcc produce better warnings (and possibly even better code). Later, fd1d672 (usage.c: add warning_errno() and error_errno(), 2016-05-08) introduced another variant, and subsequent commits converted some uses of error() to error_errno(), losing the magic from e208f9c for those sites. As a result, compiling vcs-svn/svndiff.c with "gcc -O3" produces -Wmaybe-uninitialized false positives (at least with gcc 6.2.0). Let's give error_errno() the same treatment, which silences these warnings. Signed-off-by: Jeff King Signed-off-by: Junio C Hamano --- usage.c | 1 + 1 file changed, 1 insertion(+) (limited to 'usage.c') diff --git a/usage.c b/usage.c index 1dad03fb5..0efa3faf6 100644 --- a/usage.c +++ b/usage.c @@ -148,6 +148,7 @@ void NORETURN die_errno(const char *fmt, ...) va_end(params); } +#undef error_errno int error_errno(const char *fmt, ...) { char buf[1024]; -- cgit v1.2.1