mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: John Garry <john.garry@huawei.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	jolsa@redhat.com, masahiroy@kernel.org,
	Laura Abbott <labbott@kernel.org>
Cc: peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, namhyung@kernel.org,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	irogers@google.com
Subject: Re: [PATCH] perf tools: Enable warnings through HOSTCFLAGS
Date: Mon, 15 Nov 2021 14:44:59 -0300	[thread overview]
Message-ID: <239840A9-F713-4FED-B638-14D6B91FBBF2@gmail.com> (raw)
In-Reply-To: <591edce2-5aaa-22bc-6fd3-5a247f623eb3@huawei.com>



On November 15, 2021 12:53:33 PM GMT-03:00, John Garry <john.garry@huawei.com> wrote:
>On 06/11/2021 19:27, Arnaldo Carvalho de Melo wrote:
>> Em Sat, Oct 30, 2021 at 12:30:41AM +0800, John Garry escreveu:
>>> The tools build system uses KBUILD_HOSTCFLAGS symbol for obvious purposes.
>>>
>>> However this is not set for anything under tools/
>>>
>>> As such, host tools apps built have no compiler warnings enabled.
>>>
>>> Declare HOSTCFLAGS for perf tools build, and also use that symbol in
>>> declaration of host_c_flags. HOSTCFLAGS comes from EXTRA_WARNINGS, which
>>> is independent of target platform/arch warning flags.
>>>
>>> Suggested-by: Jiri Olsa <jolsa@redhat.com>
>>> Signed-off-by: John Garry <john.garry@huawei.com>
>>> --
>>> Using HOSTCFLAGS, as opposed to KBUILD_HOSTCFLAGS, is going opposite
>>> direction to commit 96f14fe738b6 ("kbuild: Rename HOSTCFLAGS to
>>> KBUILD_HOSTCFLAGS"), so would like further opinion from Laura and
>>> Masahiro.
>> 
>> Laura's redhat e-mail bouncedm updated it to her kernel.org one, Laura,
>> Masahiro, would you please comment? Jiri?
>
>Any opinion on this one? Shall I just resend ... ? or just apply it if 
>no one cares too much :)

I'll apply it now that everybody got enough time to review it . :-)

- Arnaldo
>
>Thanks,
>John
>
>> 
>> - Arnaldo
>>   
>>> diff --git a/tools/build/Build.include b/tools/build/Build.include
>>> index 2cf3b1bde86e..c2a95ab47379 100644
>>> --- a/tools/build/Build.include
>>> +++ b/tools/build/Build.include
>>> @@ -99,7 +99,7 @@ cxx_flags = -Wp,-MD,$(depfile) -Wp,-MT,$@ $(CXXFLAGS) -D"BUILD_STR(s)=\#s" $(CXX
>>>   ###
>>>   ## HOSTCC C flags
>>>   
>>> -host_c_flags = -Wp,-MD,$(depfile) -Wp,-MT,$@ $(KBUILD_HOSTCFLAGS) -D"BUILD_STR(s)=\#s" $(HOSTCFLAGS_$(basetarget).o) $(HOSTCFLAGS_$(obj))
>>> +host_c_flags = -Wp,-MD,$(depfile) -Wp,-MT,$@ $(HOSTCFLAGS) -D"BUILD_STR(s)=\#s" $(HOSTCFLAGS_$(basetarget).o) $(HOSTCFLAGS_$(obj))
>>>   
>>>   # output directory for tests below
>>>   TMPOUT = .tmp_$$$$
>>> diff --git a/tools/perf/Makefile.config b/tools/perf/Makefile.config
>>> index 4a9baed28f2e..9b95ba09657f 100644
>>> --- a/tools/perf/Makefile.config
>>> +++ b/tools/perf/Makefile.config
>>> @@ -17,6 +17,7 @@ detected     = $(shell echo "$(1)=y"       >> $(OUTPUT).config-detected)
>>>   detected_var = $(shell echo "$(1)=$($(1))" >> $(OUTPUT).config-detected)
>>>   
>>>   CFLAGS := $(EXTRA_CFLAGS) $(filter-out -Wnested-externs,$(EXTRA_WARNINGS))
>>> +HOSTCFLAGS := $(filter-out -Wnested-externs,$(EXTRA_WARNINGS))
>>>   
>>>   include $(srctree)/tools/scripts/Makefile.arch
>>>   
>>> @@ -211,6 +212,7 @@ endif
>>>   ifneq ($(WERROR),0)
>>>     CORE_CFLAGS += -Werror
>>>     CXXFLAGS += -Werror
>>> +  HOSTCFLAGS += -Werror
>>>   endif
>>>   
>>>   ifndef DEBUG
>>> @@ -292,6 +294,9 @@ CXXFLAGS += -ggdb3
>>>   CXXFLAGS += -funwind-tables
>>>   CXXFLAGS += -Wno-strict-aliasing
>>>   
>>> +HOSTCFLAGS += -Wall
>>> +HOSTCFLAGS += -Wextra
>>> +
>>>   # Enforce a non-executable stack, as we may regress (again) in the future by
>>>   # adding assembler files missing the .GNU-stack linker note.
>>>   LDFLAGS += -Wl,-z,noexecstack
>>> diff --git a/tools/perf/Makefile.perf b/tools/perf/Makefile.perf
>>> index a3966f290297..8ca656aa8b06 100644
>>> --- a/tools/perf/Makefile.perf
>>> +++ b/tools/perf/Makefile.perf
>>> @@ -226,7 +226,7 @@ else
>>>   endif
>>>   
>>>   export srctree OUTPUT RM CC CXX LD AR CFLAGS CXXFLAGS V BISON FLEX AWK
>>> -export HOSTCC HOSTLD HOSTAR
>>> +export HOSTCC HOSTLD HOSTAR HOSTCFLAGS
>>>   
>>>   include $(srctree)/tools/build/Makefile.include
>>>   
>>> -- 
>>> 2.17.1
>> 
>

  reply	other threads:[~2021-11-16  1:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 16:30 John Garry
2021-11-01 21:10 ` Arnaldo Carvalho de Melo
2021-11-06 19:27 ` Arnaldo Carvalho de Melo
2021-11-15 15:53   ` John Garry
2021-11-15 17:44     ` Arnaldo Carvalho de Melo [this message]
2021-11-15 21:10       ` Jiri Olsa

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=239840A9-F713-4FED-B638-14D6B91FBBF2@gmail.com \
    --to=arnaldo.melo@gmail.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=john.garry@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=labbott@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®