From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] building libtraceevent with clang
Date: Fri, 17 Feb 2017 10:44:37 -0300 [thread overview]
Message-ID: <20170217134437.GC4109@kernel.org> (raw)
In-Reply-To: <20170216210023.5c39de2f@grimm.local.home>
Em Thu, Feb 16, 2017 at 09:00:23PM -0500, Steven Rostedt escreveu:
> On Mon, 13 Feb 2017 14:20:20 -0300
> Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > +++ b/tools/lib/traceevent/plugin_function.c
> > @@ -130,7 +130,7 @@ static int function_handler(struct trace_seq *s, struct pevent_record *record,
> > unsigned long long pfunction;
> > const char *func;
> > const char *parent;
> > - int index;
> > + int index = 0;
> I went to apply this to trace-cmd's version, and it failed to apply. Then I
> realized that I had this fixed back in 2015, but missed sending it.
> That's because I don't strictly follow the 80 column limit for some of the if
> statements (I find the break up ugly), and when doing diffs, this got lost in
> the diffs of the 80 column limits ones done with the port to the kernel tree.
> :-/
I'm not strict about it either:
$ find tools/perf/ -name "*.[ch]" | xargs cat | wc -l
161984
$ find tools/perf/ -name "*.[ch]" | xargs expand | cut -c80- | grep -v ^$ | wc -l
3706
$
2.29%
You (well, libtracevent) are a bit more strict:
$ find tools/lib/traceevent/ -name "*.[ch]" | xargs cat | wc -l
13814
$ find tools/lib/traceevent/ -name "*.[ch]" | xargs expand | cut -c80- | grep -v ^$ | wc -l
184
$
1.33%
For reference, the whole kernel, modulo tools/
$ find . -name "*.[ch]" | grep -v ^\.\/tools | xargs cat | wc -l
20162880
$ find . -name "*.[ch]" | grep -v ^\.\/tools | xargs expand | cut -c80- | grep -v ^$ | wc -l
439722
$
2.18%
Using functions to avoid too deep if statements usually helps here tho :-)
- Arnaldo
> -- Steve
>
>
> >
> > if (pevent_get_field_val(s, event, "ip", record, &function, 1))
> > return trace_seq_putc(s, '!');
> >
next prev parent reply other threads:[~2017-02-17 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 17:03 [PATCH] building libtraceevent with clang Arnaldo Carvalho de Melo
2017-02-10 19:14 ` Steven Rostedt
2017-02-13 16:24 ` Arnaldo Carvalho de Melo
2017-02-13 16:26 ` Arnaldo Carvalho de Melo
2017-02-13 17:14 ` Steven Rostedt
2017-02-13 17:20 ` Arnaldo Carvalho de Melo
2017-02-13 17:46 ` Steven Rostedt
2017-02-17 2:00 ` Steven Rostedt
2017-02-17 13:44 ` Arnaldo Carvalho de Melo [this message]
2017-02-14 6:40 ` [tip:perf/core] tools lib traceevent: Initialize lenght on OLD_RING_BUFFER_TYPE_TIME_STAMP tip-bot for Steven Rostedt (VMware)
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=20170217134437.GC4109@kernel.org \
--to=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
/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.