DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Yang, Yi" <yi.y.yang@intel.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] service: fix compilation error
Date: Thu, 21 Sep 2017 09:50:00 +0800	[thread overview]
Message-ID: <20170921014959.GA119171@cran64.bj.intel.com> (raw)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA650FA5C48@IRSMSX101.ger.corp.intel.com>

On Wed, Sep 20, 2017 at 05:00:11PM +0800, Van Haaren, Harry wrote:
> > From: Yang, Yi Y
> > Sent: Wednesday, September 20, 2017 9:31 AM
> > To: Van Haaren, Harry <harry.van.haaren@intel.com>
> > Cc: dev@dpdk.org; Yang, Yi Y <yi.y.yang@intel.com>
> > Subject: [PATCH] service: fix compilation error
> > 
> >   CC rte_service.o
> >   ./dpdk/lib/librte_eal/common/rte_service.c: In function
> >     ‘rte_service_start_with_defaults’:
> >   ./dpdk/lib/librte_eal/common/rte_service.c:449:9:
> >     error: ‘ids[0]’ may be used uninitialized in this
> >     function [-Werror=maybe-uninitialized]
> >    ret = rte_service_map_lcore_set(i, ids[lcore_iter], 1);
> > 
> >   cc1: all warnings being treated as errors
> >   ./dpdk/mk/internal/rte.compile-pre.mk:138:
> >     recipe for target 'rte_service.o' failed
> > 
> > Signed-off-by: Yi Yang <yi.y.yang@intel.com>
> 
> Hi Yi,
> 
> Would you provide a more descriptive commit title
> and message please? The compilation output should not be
> included in the commit message, instead a short description
> of what the error is, and what steps can be taken to
> reproduce the error are much more helpful.
> 
> The code changes look OK to me - but I'd like to be able
> to catch these issues in future, so steps to reproduce are
> valuable to me.
> 
> Thanks, -Harry

Harry, normal DPDK make everybody does usually will trigger
this on current master tree, I'm not sure if it is gcc version
related. On my Fedora 21, it can be reproduced very easily.
I met it when I fixed another vhost bug, I can't build DPDK
without it, that is why I want to commit it to you :-)

I have posted out v2 with more descriptive title and git log
body per your comments. Thanks a lot for your review.

> 
> 
> > ---
> >  lib/librte_eal/common/rte_service.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/lib/librte_eal/common/rte_service.c
> > b/lib/librte_eal/common/rte_service.c
> > index 43716bb..e598e16 100644
> > --- a/lib/librte_eal/common/rte_service.c
> > +++ b/lib/librte_eal/common/rte_service.c
> > @@ -431,7 +431,7 @@ rte_service_start_with_defaults(void)
> >  	uint32_t count = rte_service_get_count();
> > 
> >  	int32_t lcore_iter = 0;
> > -	uint32_t ids[RTE_MAX_LCORE];
> > +	uint32_t ids[RTE_MAX_LCORE] = {0};
> >  	int32_t lcore_count = rte_service_lcore_list(ids, RTE_MAX_LCORE);
> > 
> >  	if (lcore_count == 0)
> > --
> > 2.1.0
> 

      reply	other threads:[~2017-09-21  2:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20  8:31 Yi Yang
2017-09-20  9:00 ` Van Haaren, Harry
2017-09-21  1:50   ` Yang, Yi [this message]

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=20170921014959.GA119171@cran64.bj.intel.com \
    --to=yi.y.yang@intel.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@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).