From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] [RFC] [PATCH] -Werror=old-style-definition and UST tracepoints
Date: Mon, 11 Jun 2012 09:52:29 -0400 [thread overview]
Message-ID: <20120611135229.GA18709@Krystal> (raw)
In-Reply-To: <4FD243CF.60104@mentor.com>
* Hollis Blanchard (hollis_blanchard at mentor.com) wrote:
[...]
> I believe the problem comes from -Werror=old-style-definition not liking
> that empty "()", i.e. tracepoint_cb_qemu_tb_hash___flushall() { ... }.
> The following patch seems to work for me; is there a reason it isn't
> already written this way?
Good catch !
Fixed as master commit:
commit 86637aa6452f66dee5f769461668c2ea059b3a30
Author: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
Date: Mon Jun 11 09:53:07 2012 -0400
Fix: tracepoint.h should not generate old-style definitions
and merged into stable-2.0.
Thanks!
Mathieu
>
> diff --git a/include/lttng/tracepoint.h b/include/lttng/tracepoint.h
>
> index 4b773bb..60d8c73 100644
>
> --- a/include/lttng/tracepoint.h
>
> +++ b/include/lttng/tracepoint.h
>
> @@ -88,7 +88,7 @@ extern "C" {
>
> #define _TP_EXDATA_VAR20(a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t) __tp_data,b,d,f,h,j,l,n,p,r,t
>
>
>
> /* _TP_EXPROTO* extract tuples of type, var */
>
> -#define _TP_EXPROTO0()
>
> +#define _TP_EXPROTO0() void
>
> #define _TP_EXPROTO2(a,b) a b
>
> #define _TP_EXPROTO4(a,b,c,d) a b,c d
>
> #define _TP_EXPROTO6(a,b,c,d,e,f) a b,c d,e f
>
>
> If this is OK, I'm happy to resend as a proper patch.
>
> --
> Hollis Blanchard
> Mentor Graphics, Embedded Systems Division
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2012-06-11 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 18:26 Hollis Blanchard
2012-06-11 13:52 ` Mathieu Desnoyers [this message]
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=20120611135229.GA18709@Krystal \
--to=mathieu.desnoyers@efficios.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox