From: Masami Hiramatsu <mhiramat@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Leo Yan <leo.yan@linaro.org>,
linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: [PATCH 0/2] tools/perf: tools: Fix perf build issues
Date: Wed, 12 May 2021 00:02:25 +0900 [thread overview]
Message-ID: <162074534493.289757.1243545574686276554.stgit@devnote2> (raw)
Hi,
These are the patches to fix the perf build issues which I reported in
the previous email.
https://lore.kernel.org/lkml/162037766527.94840.4323848545957010011.stgit@devnote2/
There are 2 issues I found and are fixed with these patches.
- Since the EXTRA_CLFAGS/WARNINGS are listed before -Wall/-Wextra in
CFLAGS, all -Wno-* flags in the EXTRA_CFLAGS/WARNINGS are ignored.
This makes EXTRA_WARNINGS ignored and developers can not use EXTRA_CLFAGS
for debugging compiler warnings.
- Clang's missing-field-initializers warning is too sensitive compared
with GCC. I think "{ NULL }" kind of syntax is allowed for simplify code.
Thank you,
---
Masami Hiramatsu (2):
perf build: Move EXTRA_CFLAGS and EXTRA_WARNINGS at the end of CFLAGS
tools: Add -Wno-missing-field-initializers to for clang
tools/perf/Makefile.config | 3 ++-
tools/scripts/Makefile.include | 4 ++++
2 files changed, 6 insertions(+), 1 deletion(-)
--
Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
next reply other threads:[~2021-05-11 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 15:02 Masami Hiramatsu [this message]
2021-05-11 15:02 ` [PATCH 1/2] perf build: Move EXTRA_CFLAGS and EXTRA_WARNINGS at the end of CFLAGS Masami Hiramatsu
2021-05-11 15:02 ` [PATCH 2/2] tools: Add -Wno-missing-field-initializers to for clang Masami Hiramatsu
2021-05-11 18:23 ` Nick Desaulniers
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=162074534493.289757.1243545574686276554.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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