From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Ali Alnubani <alialnu@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Khangar, Churchill" <churchill.khangar@intel.com>
Subject: Re: [dpdk-dev] [PATCH] examples/pipeline: fix build
Date: Mon, 12 Jul 2021 08:08:28 +0000 [thread overview]
Message-ID: <DM8PR11MB5670C957E89917D2758D720AEB159@DM8PR11MB5670.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210712074636.406903-1-alialnu@nvidia.com>
> -----Original Message-----
> From: Ali Alnubani <alialnu@nvidia.com>
> Sent: Monday, July 12, 2021 8:47 AM
> To: dev@dpdk.org
> Cc: thomas@monjalon.net; Khangar, Churchill
> <churchill.khangar@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>
> Subject: [PATCH] examples/pipeline: fix build
>
> This patch fixes the following build failures seen on Ubuntu 16.04
> with gcc 5.4.0 because of uninitialized variables:
> ...
> examples/pipeline/cli.c:1559:11: error: 'weight_val' may be used
> uninitialized in this function [-Werror=maybe-uninitialized]
> ...
> examples/pipeline/cli.c:1545:13: error: 'member_id_val' may be used
> uninitialized in this function [-Werror=maybe-uninitialized]
> ...
> examples/pipeline/cli.c:1538:12: error: 'group_id_val' may be used
> uninitialized in this function [-Werror=maybe-uninitialized]
> ...
> examples/pipeline/cli.c:2189:2: error: 'idx1' may be used
> uninitialized in this function [-Werror=maybe-uninitialized]
> ...
> examples/pipeline/cli.c:2179:43: error: 'idx0' may be used
> uninitialized in this function [-Werror=maybe-uninitialized]
> ...
> examples/pipeline/cli.c:2265:2: error: 'idx1' may be used
> uninitialized in this function [-Werror=maybe-uninitialized]
> ...
> examples/pipeline/cli.c:2248:43: error: 'idx0' may be used
> uninitialized in this function [-Werror=maybe-uninitialized]
> ...
> examples/pipeline/cli.c:2358:2: error: 'idx1' may be used
> uninitialized in this function [-Werror=maybe-uninitialized]
> ...
> examples/pipeline/cli.c:2325:43: error: 'idx0' may be used
> uninitialized in this function [-Werror=maybe-uninitialized]
>
> Fixes: 598fe0dd0d8e ("examples/pipeline: support selector table")
> Cc: cristian.dumitrescu@intel.com
>
> Signed-off-by: Ali Alnubani <alialnu@nvidia.com>
> ---
> examples/pipeline/cli.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
next prev parent reply other threads:[~2021-07-12 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 7:46 Ali Alnubani
2021-07-12 8:08 ` Dumitrescu, Cristian [this message]
2021-07-20 10:04 ` 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=DM8PR11MB5670C957E89917D2758D720AEB159@DM8PR11MB5670.namprd11.prod.outlook.com \
--to=cristian.dumitrescu@intel.com \
--cc=alialnu@nvidia.com \
--cc=churchill.khangar@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).