DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Jingjing Wu <jingjing.wu@intel.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	dev@dpdk.org, Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-dev] [PATCH] net/avf: remove unused variables and label
Date: Mon, 17 Sep 2018 17:24:53 +0100	[thread overview]
Message-ID: <20180917162453.GC4520@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <9f2a9d42-2862-c5bd-8021-49198765762b@intel.com>

On Mon, Sep 17, 2018 at 05:12:19PM +0100, Ferruh Yigit wrote:
> On 9/17/2018 4:20 PM, Bruce Richardson wrote:
> > On Mon, Sep 17, 2018 at 03:53:40PM +0100, Ferruh Yigit wrote:
> >> On 9/13/2018 3:44 PM, Bruce Richardson wrote:
> >>> Compiling with all warnings turned on causes errors about unused variables
> >>> and an unused label. Remove these to allow building without having to
> >>> disable those warnings.
> >>
> >> If this is fixing some build errors should it be backported?
> >>
> >> And why we didn't get those warnings until now, aren't we already compiling with
> >> all warnings turned on?
> >>
> >>>
> >>> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> >>
> > It does not appear so. When we add support for building this driver with
> > meson, the compiler warnings then appeared [See
> > http://patches.dpdk.org/patch/44698/]. 
> > 
> > While you can backport I'm not sure it's worthwhile, unless you plan on
> > backporting the new meson support too.  The warnings don't come from
> > external header files that apps would be using directly with unknown
> > compiler flags, but are internal to DPDK and don't seem to cause any issues
> > with "make" builds.
> 
> Argh, it is missing warning flags in Makefile:
>  +CFLAGS += $(WERROR_FLAGS)
> 
> When above added "make" also gives "unused variable" warnings.
> 
> Even we don't observe the issue with current makefile, if someone builds with:
> 'make  EXTRA_CFLAGS="-Wunused-variable"' will observe the warnings.
> 
> That is why I am for backporting this patch, does it make sense?
> 
> And would you mind adding above CFLAGS update into this patch?

Ok, I'll do up a V2.

  reply	other threads:[~2018-09-17 16:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13 14:44 Bruce Richardson
2018-09-13 16:26 ` Luca Boccassi
2018-09-17  7:23   ` Zhang, Qi Z
2018-09-17 14:53 ` Ferruh Yigit
2018-09-17 15:20   ` Bruce Richardson
2018-09-17 16:12     ` Ferruh Yigit
2018-09-17 16:24       ` Bruce Richardson [this message]
2018-09-18 13:17 ` [dpdk-dev] [PATCH v2 1/2] net/avf: fix " Bruce Richardson
2018-09-18 13:17   ` [dpdk-dev] [PATCH v2 2/2] net/avf: fix missing compiler error flags Bruce Richardson
2018-09-18 13:54     ` Ferruh Yigit
2018-09-18 13:51   ` [dpdk-dev] [PATCH v2 1/2] net/avf: fix unused variables and label Ferruh Yigit
2018-09-18 14:18     ` Bruce Richardson
2018-09-18 14:22   ` [dpdk-dev] [PATCH v3 " Bruce Richardson
2018-09-18 14:22     ` [dpdk-dev] [PATCH v3 2/2] net/avf: fix missing compiler error flags Bruce Richardson
2018-09-19 10:04 ` [dpdk-dev] [PATCH v4 0/3] AVF build improvements Bruce Richardson
2018-09-19 10:04   ` [dpdk-dev] [PATCH v4 1/3] net/avf: fix unused variables and label Bruce Richardson
2018-09-19 10:04   ` [dpdk-dev] [PATCH v4 2/3] net/avf: fix missing compiler error flags Bruce Richardson
2018-09-19 10:04   ` [dpdk-dev] [PATCH v4 3/3] build: add meson files for AVF PMD Bruce Richardson
2018-09-21 14:43   ` [dpdk-dev] [PATCH v4 0/3] AVF build improvements Zhang, Qi Z

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=20180917162453.GC4520@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=wenzhuo.lu@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;
as well as URLs for NNTP newsgroup(s).