mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: James Clark <james.clark@arm.com>, <peterz@infradead.org>,
	<acme@kernel.org>, <mark.rutland@arm.com>,
	<alexander.shishkin@linux.intel.com>, <jolsa@redhat.com>,
	<namhyung@kernel.org>, <mingo@redhat.com>
Cc: <irogers@google.com>, <linux-perf-users@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <kjain@linux.ibm.com>
Subject: Re: [PATCH 2/2] perf jevents: Enable warnings through HOSTCFLAGS
Date: Tue, 19 Oct 2021 09:37:23 +0100	[thread overview]
Message-ID: <89695366-c729-492e-aad6-5c98f914da79@huawei.com> (raw)
In-Reply-To: <1804d7f3-c3bb-a90f-c86d-d96bff4235d2@arm.com>

On 18/10/2021 11:41, James Clark wrote:
> 
> 
> On 15/10/2021 17:48, John Garry wrote:
>> Currently no compiler warnings at all are enabled for building jevents,
>> so help catch bugs at compile time by enabling through HOSTCFLAGS.
> 

Hi James,

> Is there any reason to not enable -Wall and -Werror so that it builds like
> the main project? Or if HOSTCFLAGS ends up being the same as CORE_CFLAGS
> then why not use CORE_CFLAGS instead?

I am not sure that we really want that, as CORE_CFLAGS brings with it 
things like _LARGEFILE64_SOURCE, which I doubt we want.

> 
> I added them like this and only one unused function needs to be removed to
> make it build successfully:
> 
> 
> diff --git a/tools/perf/Makefile.config b/tools/perf/Makefile.config
> index 65934984f032..b2edcedf01db 100644
> --- a/tools/perf/Makefile.config
> +++ b/tools/perf/Makefile.config
> @@ -18,6 +18,8 @@ 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))
> +HOSTCFLAGS += -Wall
> +HOSTCFLAGS += -Wextra
>   
>   include $(srctree)/tools/scripts/Makefile.arch
>   
> @@ -212,6 +214,7 @@ endif
>   ifneq ($(WERROR),0)
>     CORE_CFLAGS += -Werror
>     CXXFLAGS += -Werror
> +  HOSTCFLAGS += -Werror

These seem fine to add. Actually what I have in HOSTCFLAGS doesn't seem 
to detect unused functions, with one example fixed in b94729919db2.

Thanks,
John

  reply	other threads:[~2021-10-19  8:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 16:48 [PATCH 0/2] perf jevents: Enable build warnings John Garry
2021-10-15 16:48 ` [PATCH 1/2] perf jevents: Fix some would-be warnings John Garry
2021-10-15 16:48 ` [PATCH 2/2] perf jevents: Enable warnings through HOSTCFLAGS John Garry
2021-10-18 10:41   ` James Clark
2021-10-19  8:37     ` John Garry [this message]
2021-10-20 14:31 ` [PATCH 0/2] perf jevents: Enable build warnings Arnaldo Carvalho de Melo
2021-10-20 14:41   ` John Garry
2021-10-20 16:34     ` Arnaldo Carvalho de Melo
2021-10-20 17:25     ` Arnaldo Carvalho de Melo
2021-10-21 20:31       ` [RFC] Support Intel-PT code build in 32-bit arches Arnaldo Carvalho de Melo
2021-10-22 12:23         ` Adrian Hunter

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=89695366-c729-492e-aad6-5c98f914da79@huawei.com \
    --to=john.garry@huawei.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@redhat.com \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --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®