From: Taeung Song <taeung.dev@gmail.com>
To: Vinson Lee <vlee@freedesktop.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Taeung Song <treeze.taeung@gmail.com>,
Jiri Olsa <jolsa@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Alexei Starovoitov <ast@plumgrid.com>,
Wang Nan <wangnan0@huawei.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf config: Fix build with older toolchain.
Date: Tue, 5 Apr 2016 14:24:19 +0900 [thread overview]
Message-ID: <57034C03.2030603@gmail.com> (raw)
In-Reply-To: <1459807659-9020-1-git-send-email-vlee@freedesktop.org>
Hi,
On 04/05/2016 07:07 AM, Vinson Lee wrote:
> Fix build error on Ubuntu 12.04.5 with GCC 4.6.3.
>
> CC util/config.o
> util/config.c: In function ‘perf_buildid_config’:
> util/config.c:384:15: error: declaration of ‘dirname’ shadows a global declaration [-Werror=shadow]
I'm sorry, lately I added perf_buildid_config() but I didn't test by
gcc-4.6.3
> Fixes: 9cb5987c8227 ("perf config: Rework buildid_dir_command_config to perf_buildid_config")
> Signed-off-by: Vinson Lee <vlee@freedesktop.org>
> ---
> tools/perf/util/config.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/util/config.c b/tools/perf/util/config.c
> index 5c20d783423b..a3d80a05e7a2 100644
> --- a/tools/perf/util/config.c
> +++ b/tools/perf/util/config.c
> @@ -381,11 +381,11 @@ static int perf_buildid_config(const char *var, const char *value)
> {
> /* same dir for all commands */
> if (!strcmp(var, "buildid.dir")) {
> - const char *dirname = perf_config_dirname(var, value);
> + const char *v = perf_config_dirname(var, value);
Why you use 'v' variable name ?
'v' variable name was used in set_buildid_dir(), too.
But I send a patch renaming 'v' to 'home' because 'home' is more readable.
37194f4 ("perf config: Rename 'v' to 'home' in set_buildid_dir()")
https://lkml.org/lkml/2016/3/27/98
IMHO, I like using 'dir' instead of 'v'.
Thanks,
Taeung
>
> - if (!dirname)
> + if (!v)
> return -1;
> - strncpy(buildid_dir, dirname, MAXPATHLEN-1);
> + strncpy(buildid_dir, v, MAXPATHLEN-1);
> buildid_dir[MAXPATHLEN-1] = '\0';
> }
>
>
next prev parent reply other threads:[~2016-04-05 5:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 22:07 [PATCH] perf config: Fix build with older toolchain Vinson Lee
2016-04-05 5:24 ` Taeung Song [this message]
2016-04-05 13:38 ` Arnaldo Carvalho de Melo
2016-04-05 13:47 ` Taeung Song
2016-04-05 13:36 ` Arnaldo Carvalho de Melo
2016-04-13 7:12 ` [tip:perf/core] " tip-bot for Vinson Lee
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=57034C03.2030603@gmail.com \
--to=taeung.dev@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ast@plumgrid.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=treeze.taeung@gmail.com \
--cc=vlee@freedesktop.org \
--cc=wangnan0@huawei.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