From: Junio C Hamano <gitster@pobox.com>
To: Thomas Rast <tr@thomasrast.ch>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH v2] commit-slab: declare functions "static inline"
Date: Mon, 25 Nov 2013 12:23:58 -0800 [thread overview]
Message-ID: <xmqqmwksxmap.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <89b534b37f5689a675f0f97d3627a0668ce2a71d.1385409724.git.tr@thomasrast.ch> (Thomas Rast's message of "Mon, 25 Nov 2013 21:04:08 +0100")
Thomas Rast <tr@thomasrast.ch> writes:
> Here's a version that has a fat comment instead of the removal.
>
> Also, since I was rerolling anyway I put a reason why we need this.
> In the original motivation I actually created more functions
> afterwards, which made it more convincing, but the problem already
> exists.
Thanks.
I considered the bottom one the real declaration (with the top one a
forward declaration we need to make the result compile), by the way,
so there may be no redundancy anywhere ;-)
> commit-slab.h | 24 ++++++++++++++++++------
> 1 file changed, 18 insertions(+), 6 deletions(-)
>
> diff --git a/commit-slab.h b/commit-slab.h
> index d77aaea..21d54f1 100644
> --- a/commit-slab.h
> +++ b/commit-slab.h
> @@ -45,8 +45,8 @@ struct slabname { \
> }; \
> static int stat_ ##slabname## realloc; \
> \
> -static void init_ ##slabname## _with_stride(struct slabname *s, \
> - unsigned stride) \
> +static inline void init_ ##slabname## _with_stride(struct slabname *s, \
> + unsigned stride) \
> { \
> unsigned int elem_size; \
> if (!stride) \
> @@ -58,12 +58,12 @@ struct slabname { \
> s->slab = NULL; \
> } \
> \
> -static void init_ ##slabname(struct slabname *s) \
> +static inline void init_ ##slabname(struct slabname *s) \
> { \
> init_ ##slabname## _with_stride(s, 1); \
> } \
> \
> -static void clear_ ##slabname(struct slabname *s) \
> +static inline void clear_ ##slabname(struct slabname *s) \
> { \
> int i; \
> for (i = 0; i < s->slab_count; i++) \
> @@ -73,8 +73,8 @@ struct slabname { \
> s->slab = NULL; \
> } \
> \
> -static elemtype *slabname## _at(struct slabname *s, \
> - const struct commit *c) \
> +static inline elemtype *slabname## _at(struct slabname *s, \
> + const struct commit *c) \
> { \
> int nth_slab, nth_slot; \
> \
> @@ -98,4 +98,16 @@ struct slabname { \
> \
> static int stat_ ##slabname## realloc
>
> +/*
> + * Note that this seemingly redundant second declaration is required
> + * to allow a terminating semicolon, which makes instantiations look
> + * like function declarations. I.e., the expansion of
> + *
> + * define_commit_slab(indegree, int);
> + *
> + * ends in 'static int stat_indegreerealloc;'. This would otherwise
> + * be a syntax error according (at least) to ISO C. It's hard to
> + * catch because GCC silently parses it by default.
> + */
> +
> #endif /* COMMIT_SLAB_H */
next prev parent reply other threads:[~2013-11-25 20:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 19:01 [PATCH 0/2] commit-slab cleanups Thomas Rast
2013-11-25 19:02 ` [PATCH 1/2] commit-slab: document clear_$slabname() Thomas Rast
2013-11-25 20:24 ` Jonathan Nieder
2013-11-29 19:35 ` Thomas Rast
2013-11-25 20:39 ` Junio C Hamano
2013-11-27 10:39 ` Eric Sunshine
2013-11-25 19:02 ` [PATCH 2/2] commit-slab: declare functions "static inline" Thomas Rast
2013-11-25 19:36 ` Junio C Hamano
2013-11-25 19:53 ` Thomas Rast
2013-11-25 20:04 ` [PATCH v2] " Thomas Rast
2013-11-25 20:12 ` Jonathan Nieder
2013-11-25 20:15 ` Thomas Rast
2013-11-25 20:35 ` Jonathan Nieder
2013-11-25 20:33 ` Junio C Hamano
2013-11-25 20:23 ` Junio C Hamano [this message]
2013-12-01 10:36 ` [PATCH 2/2] " Duy Nguyen
2013-12-01 20:41 ` [PATCH] commit-slab: sizeof() the right type in xrealloc Thomas Rast
2013-12-02 15:35 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqmwksxmap.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=tr@thomasrast.ch \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.