From: "Jastrzebski, MichalX K" <michalx.k.jastrzebski@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Mrzyglod, DanielX T" <danielx.t.mrzyglod@intel.com>
Subject: Re: [PATCH] examples/ip_pipeline: fix build error for gcc 4.8
Date: Thu, 16 Jun 2016 13:35:37 +0000 [thread overview]
Message-ID: <60ABE07DBB3A454EB7FAD707B4BB158213AAB875@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <1868672.fp3FqAkN9z@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Tuesday, June 14, 2016 9:04 PM
> To: Mrzyglod, DanielX T <danielx.t.mrzyglod@intel.com>
> Cc: dev@dpdk.org; Singh, Jasvinder <jasvinder.singh@intel.com>;
> Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] examples/ip_pipeline: fix build error for gcc
> 4.8
>
> 2016-06-09 13:38, Daniel Mrzyglod:
> > This patch fixes a maybe-uninitialized warning when compiling DPDK with
> GCC 4.8
> >
> > examples/ip_pipeline/pipeline/pipeline_common_fe.c: In function
> 'app_pipeline_track_pktq_out_to_link':
> > examples/ip_pipeline/pipeline/pipeline_common_fe.c:66:31: error:
> > 'reader' may be used uninitialized in this function [-Werror=maybe-
> uninitialized]
> >
> > struct app_pktq_out_params *pktq_out =
> >
> > Fixes: 760064838ec0 ("examples/ip_pipeline: link routing output ports to
> devices")
> >
> > Signed-off-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
>
> For a weird reason, this patch triggers a new error:
>
> examples/ip_pipeline/pipeline/pipeline_common_fe.c:In function
> ‘app_pipeline_track_pktq_out_to_link’:
> examples/ip_pipeline/pipeline/pipeline_common_fe.c:124:11:
> error: ‘id’ may be used uninitialized in this function [-Werror=maybe-
> uninitialized]
> status = ptype->fe_ops->f_track(&pp,
> ^
> In file included from
> examples/ip_pipeline/pipeline/pipeline_common_fe.h:44:0,
> from examples/ip_pipeline/pipeline/pipeline_common_fe.c:47:
> examples/ip_pipeline/app.h:734:26: note: ‘id’ was declared here
> uint32_t n_readers = 0, id, i;
> ^
> examples/ip_pipeline/pipeline/pipeline_common_fe.c:97:11:
> error: ‘id’ may be used uninitialized in this function [-Werror=maybe-
> uninitialized]
> status = ptype->fe_ops->f_track(&pp,
> ^
> In file included from
> examples/ip_pipeline/pipeline/pipeline_common_fe.h:44:0,
> from examples/ip_pipeline/pipeline/pipeline_common_fe.c:47:
> examples/ip_pipeline/app.h:674:26: note: ‘id’ was declared here
> uint32_t n_readers = 0, id, i;
> ^
Hi Thomas,
Do You have this error on the same environment?
next prev parent reply other threads:[~2016-06-16 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 11:38 [PATCH] examples/ip_pipeline: fix build error for gcc 4.8 Daniel Mrzyglod
2016-06-09 10:52 ` Dumitrescu, Cristian
2016-06-14 19:04 ` Thomas Monjalon
2016-06-16 13:35 ` Jastrzebski, MichalX K [this message]
2016-06-21 9:35 ` [PATCH v2] " Daniel Mrzyglod
2016-06-21 17:43 ` Dumitrescu, Cristian
2016-06-22 8:44 ` Mrzyglod, DanielX T
2016-06-22 8:45 ` Mrzyglod, DanielX T
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=60ABE07DBB3A454EB7FAD707B4BB158213AAB875@IRSMSX109.ger.corp.intel.com \
--to=michalx.k.jastrzebski@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=danielx.t.mrzyglod@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=thomas.monjalon@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.