From: Jeff King <peff@peff.net>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: git@vger.kernel.org, pclouds@gmail.com, chriscool@tuxfamily.org,
l.s.r@web.de
Subject: Re: [PATCH v2 1/2] commit-slabs: move MAYBE_UNUSED out
Date: Tue, 23 Oct 2018 18:00:19 -0400 [thread overview]
Message-ID: <20181023220019.GA31613@sigill.intra.peff.net> (raw)
In-Reply-To: <20181023215020.18550-2-carenas@gmail.com>
On Tue, Oct 23, 2018 at 02:50:19PM -0700, Carlo Marcelo Arenas Belón wrote:
> after 36da893114 ("config.mak.dev: enable -Wunused-function", 2018-10-18)
> it is expected to be used to prevent -Wunused-function warnings for code
> that was macro generated
Makes sense.
> diff --git a/commit-slab-impl.h b/commit-slab-impl.h
> index ac1e6d409a..5c0eb91a5d 100644
> --- a/commit-slab-impl.h
> +++ b/commit-slab-impl.h
> @@ -1,10 +1,10 @@
> #ifndef COMMIT_SLAB_IMPL_H
> #define COMMIT_SLAB_IMPL_H
>
> -#define MAYBE_UNUSED __attribute__((__unused__))
> +#include "git-compat-util.h"
We shouldn't need to include git-compat-util.h, as the C files would
already do so, via this rule in CodingGuidelines:
- The first #include in C files, except in platform specific compat/
implementations, must be either "git-compat-util.h", "cache.h" or
"builtin.h". You do not have to include more than one of these.
(and if there is a case that does not, we should fix that).
> #define implement_static_commit_slab(slabname, elemtype) \
> - implement_commit_slab(slabname, elemtype, static MAYBE_UNUSED)
> + implement_commit_slab(slabname, elemtype, MAYBE_UNUSED static)
Is this hunk necessary?
> diff --git a/git-compat-util.h b/git-compat-util.h
> index 9a64998b24..e4d3967a23 100644
> --- a/git-compat-util.h
> +++ b/git-compat-util.h
> @@ -408,6 +408,8 @@ static inline char *git_find_last_dir_sep(const char *path)
> #define LAST_ARG_MUST_BE_NULL
> #endif
>
> +#define MAYBE_UNUSED __attribute__((__unused__))
> +
> #include "compat/bswap.h"
Looks good.
-Peff
next prev parent reply other threads:[~2018-10-23 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 11:34 [PATCH] khash: silence -Wunused-function Carlo Marcelo Arenas Belón
2018-10-23 15:44 ` Duy Nguyen
2018-10-23 21:50 ` [PATCH v2 0/2] delta-islands: avoid unused function messages Carlo Marcelo Arenas Belón
2018-10-23 21:50 ` [PATCH v2 1/2] commit-slabs: move MAYBE_UNUSED out Carlo Marcelo Arenas Belón
2018-10-23 22:00 ` Jeff King [this message]
2018-10-23 23:02 ` Carlo Arenas
2018-10-23 21:50 ` [PATCH v2 2/2] khash: silence -Wunused-function for delta-islands Carlo Marcelo Arenas Belón
2018-10-23 16:19 ` [PATCH] khash: silence -Wunused-function René Scharfe
2018-10-23 16:52 ` Carlo Arenas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181023220019.GA31613@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=carenas@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=pclouds@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).