From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples/l2fwd-ivshmem: fix icc compile error
Date: Fri, 22 Jul 2016 14:51:17 +0000 [thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E45123697821418F3@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <1469196816-29395-1-git-send-email-ferruh.yigit@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Friday, July 22, 2016 3:14 PM
> To: dev@dpdk.org
> Cc: Burakov, Anatoly <anatoly.burakov@intel.com>
> Subject: [PATCH] examples/l2fwd-ivshmem: fix icc compile error
>
> icc version 16.0.2, compile error:
>
> == host
> CC host.o
> /root/development/dpdk/examples/l2fwd-ivshmem/host/host.c(157):
> error #3656: variable "total_vm_packets_dropped"
> may be used before its value is set
> total_vm_packets_dropped += ctrl->vm_ports[portid].stats.dropped;
> ^
>
> Fixes: 6aa497249172 ("examples/l2fwd-ivshmem: import sample
> application")
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> examples/l2fwd-ivshmem/host/host.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/examples/l2fwd-ivshmem/host/host.c b/examples/l2fwd-
> ivshmem/host/host.c
> index cd284b7..da7b00d 100644
> --- a/examples/l2fwd-ivshmem/host/host.c
> +++ b/examples/l2fwd-ivshmem/host/host.c
> @@ -110,7 +110,8 @@ static void
> print_stats(void)
> {
> uint64_t total_packets_dropped, total_packets_tx, total_packets_rx;
> - uint64_t total_vm_packets_dropped, total_vm_packets_tx,
> total_vm_packets_rx;
> + uint64_t total_vm_packets_dropped = 0;
> + uint64_t total_vm_packets_tx, total_vm_packets_rx;
> unsigned portid;
>
> total_packets_dropped = 0;
> --
> 2.7.4
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
next prev parent reply other threads:[~2016-07-22 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 14:13 Ferruh Yigit
2016-07-22 14:51 ` Burakov, Anatoly [this message]
2016-07-22 16:00 ` 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=C6ECDF3AB251BE4894318F4E45123697821418F3@IRSMSX109.ger.corp.intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).