DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Subject: Re: [PATCH] build: fix meson warning about using compiler warning flags
Date: Fri, 21 Jan 2022 16:41:35 +0000	[thread overview]
Message-ID: <746d3b6884eeb51c2d565763a54734db0400cfbc.camel@debian.org> (raw)
In-Reply-To: <20220121155346.1994682-1-bruce.richardson@intel.com>

On Fri, 2022-01-21 at 15:53 +0000, Bruce Richardson wrote:
> Each build, meson would issue a warning reporting that the
> "warning_level" setting should be used in place of adding -Wextra
> directly to our build commands. Testing with meson 0.61 shows that the
> only difference for gcc and clang builds between warning levels 1 and
> 2 is the addition of -Wextra, so we can remove the warning by deleting
> our explicit set of Wextra and changing the build defaults to
> warning_level 2.
> 
> Fixes: 524a0d5d66b9 ("build: enable extra warnings with meson")
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> 
> NOTE1: Not putting CC stable for this patch, I don't believe it's worth
> the risk of backporting.
> 
> NOTE2: For reference, when building a test "hello world" project with
> different warning levels, the following flags are used by meson:
> 
> warning_level=0: <none>
> warning_level=1: -Wall -Winvalid-pch
> warning_level=2: -Wall -Winvalid-pch -Wextra
> warning_level=3: -Wall -Winvalid-pch -Wextra -Wpedantic
> ---
>  config/meson.build | 5 ++---
>  meson.build        | 2 +-
>  2 files changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/config/meson.build b/config/meson.build
> index ee12318d4f..7134e80e8d 100644
> --- a/config/meson.build
> +++ b/config/meson.build
> @@ -247,10 +247,9 @@ endif
>  add_project_arguments('-include', 'rte_config.h', language: 'c')
>  
> 
>  # enable extra warnings and disable any unwanted warnings
> +# -Wall is added by default at warning level 1, and -Wextra
> +# at warning level 2 (DPDK default)
>  warning_flags = [
> -        # -Wall is added by meson by default, so add -Wextra only
> -        '-Wextra',
> -
>          # additional warnings in alphabetical order
>          '-Wcast-qual',
>          '-Wdeprecated',
> diff --git a/meson.build b/meson.build
> index 1223b79d74..070243a33d 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -7,7 +7,7 @@ project('DPDK', 'C',
>          version: run_command(find_program('cat', 'more'),
>              files('VERSION'), check: true).stdout().strip(),
>          license: 'BSD',
> -        default_options: ['buildtype=release', 'default_library=static'],
> +        default_options: ['buildtype=release', 'default_library=static', 'warning_level=2'],
>          meson_version: '>= 0.49.2'
>  )
>  
> 

Acked-by: Luca Boccassi <bluca@debian.org>

-- 
Kind regards,
Luca Boccassi

  parent reply	other threads:[~2022-01-21 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 15:53 Bruce Richardson
2022-01-21 16:12 ` [PATCH v2] " Bruce Richardson
2022-01-21 16:41 ` Luca Boccassi [this message]
2022-02-02 15:34   ` [PATCH] " Thomas Monjalon

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=746d3b6884eeb51c2d565763a54734db0400cfbc.camel@debian.org \
    --to=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).