From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Jin Yao <yao.jin@linux.intel.com>,
John Garry <john.garry@huawei.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 00/10] perf parse-events: enable more flex/bison warnings
Date: Thu, 11 Jun 2020 10:07:58 -0300 [thread overview]
Message-ID: <20200611130758.GA18482@kernel.org> (raw)
In-Reply-To: <20200611090249.GC1786122@krava>
Em Thu, Jun 11, 2020 at 11:02:49AM +0200, Jiri Olsa escreveu:
> On Wed, Jun 10, 2020 at 02:50:50PM -0700, Ian Rogers wrote:
> > All C compiler warnings are disabled are disabled by -w. This change
> > removes the -w from flex and bison targets. To avoid implicit
> > declarations header files are declared as targets and included.
> >
> > Tested with GCC 9.3.0 and clang 9.0.1.
> >
> > Previously posted as a single change:
> > https://lore.kernel.org/lkml/20200609234344.3795-2-irogers@google.com/
> >
> > Ian Rogers (10):
> > perf parse-events: Use automatic variable for flex input
> > perf parse-events: Use automatic variable for yacc input
> > perf pmu: Add bison debug build flag
> > perf pmu: Add flex debug build flag
> > perf parse-events: Declare flex header file output
> > perf parse-events: Declare bison header file output
> > perf parse-events: Disable a subset of flex warnings
> > perf expr: Avoid implicit lex function declaration
> > perf parse-events: Avoid implicit lex function declaration
> > perf parse-events: Disable a subset of bison warnings
>
> looks great, I wonder what the -w replacement will do in
> Arnaldo's distro test, but it'd be nice to get rid it
>
> Acked-by: Jiri Olsa <jolsa@redhat.com>
Thanks, applied locally and will submit it to the test build suite.
- Arnaldo
> thanks,
> jirka
>
> >
> > tools/perf/util/Build | 50 +++++++++++++++++++++-------------
> > tools/perf/util/expr.y | 2 ++
> > tools/perf/util/parse-events.y | 1 +
> > 3 files changed, 34 insertions(+), 19 deletions(-)
> >
> > --
> > 2.27.0.278.ge193c7cf3a9-goog
> >
>
--
- Arnaldo
next prev parent reply other threads:[~2020-06-11 13:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 21:50 [PATCH 00/10] perf parse-events: enable more flex/bison warnings Ian Rogers
2020-06-10 21:50 ` [PATCH 01/10] perf parse-events: Use automatic variable for flex input Ian Rogers
2020-06-10 21:50 ` [PATCH 02/10] perf parse-events: Use automatic variable for yacc input Ian Rogers
2020-06-10 21:50 ` [PATCH 03/10] perf pmu: Add bison debug build flag Ian Rogers
2020-06-10 21:50 ` [PATCH 04/10] perf pmu: Add flex " Ian Rogers
2020-06-10 21:50 ` [PATCH 05/10] perf parse-events: Declare flex header file output Ian Rogers
2020-06-10 21:50 ` [PATCH 06/10] perf parse-events: Declare bison " Ian Rogers
2020-06-10 21:50 ` [PATCH 07/10] perf parse-events: Disable a subset of flex warnings Ian Rogers
2020-06-10 21:50 ` [PATCH 08/10] perf expr: Avoid implicit lex function declaration Ian Rogers
2020-06-10 21:50 ` [PATCH 09/10] perf parse-events: " Ian Rogers
2020-06-10 21:51 ` [PATCH 10/10] perf parse-events: Disable a subset of bison warnings Ian Rogers
2020-06-11 9:02 ` [PATCH 00/10] perf parse-events: enable more flex/bison warnings Jiri Olsa
2020-06-11 13:07 ` Arnaldo Carvalho de Melo [this message]
2020-06-11 13:38 ` Arnaldo Carvalho de Melo
2020-06-11 13:40 ` Arnaldo Carvalho de Melo
2020-06-11 13:41 ` Arnaldo Carvalho de Melo
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=20200611130758.GA18482@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yao.jin@linux.intel.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