From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Gajdzica, MaciejX T" <maciejx.t.gajdzica@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 02/11] ip_pipeline: added config checks
Date: Thu, 02 Jul 2015 13:44:12 +0200 [thread overview]
Message-ID: <2202302.jFYeIEhALS@xps13> (raw)
In-Reply-To: <9CC680510C0AC140A846FED2EF7F962813849F31@IRSMSX102.ger.corp.intel.com>
2015-07-02 10:28, Gajdzica, MaciejX T:
> For me it compiles. Could you provide build log?
OK. I think the problem is seen with GCC 5 (I use 5.1.0):
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:587:49: error: array subscript is above array bounds [-Werror=array-bounds]
struct app_pktq_in_params *pktq = &p->pktq_in[j];
^
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:587:49: error: array subscript is above array bounds [-Werror=array-bounds]
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:694:51: error: array subscript is above array bounds [-Werror=array-bounds]
struct app_pktq_out_params *pktq = &p->pktq_out[j];
^
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:694:51: error: array subscript is above array bounds [-Werror=array-bounds]
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:609:49: error: array subscript is above array bounds [-Werror=array-bounds]
struct app_pktq_in_params *pktq = &p->pktq_in[j];
^
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:609:49: error: array subscript is above array bounds [-Werror=array-bounds]
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:716:51: error: array subscript is above array bounds [-Werror=array-bounds]
struct app_pktq_out_params *pktq = &p->pktq_out[j];
^
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:716:51: error: array subscript is above array bounds [-Werror=array-bounds]
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:631:49: error: array subscript is above array bounds [-Werror=array-bounds]
struct app_pktq_in_params *pktq = &p->pktq_in[j];
^
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:631:49: error: array subscript is above array bounds [-Werror=array-bounds]
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:738:51: error: array subscript is above array bounds [-Werror=array-bounds]
struct app_pktq_out_params *pktq = &p->pktq_out[j];
^
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:738:51: error: array subscript is above array bounds [-Werror=array-bounds]
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:654:49: error: array subscript is above array bounds [-Werror=array-bounds]
struct app_pktq_in_params *pktq = &p->pktq_in[j];
^
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:654:49: error: array subscript is above array bounds [-Werror=array-bounds]
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:760:51: error: array subscript is above array bounds [-Werror=array-bounds]
struct app_pktq_out_params *pktq = &p->pktq_out[j];
^
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:760:51: error: array subscript is above array bounds [-Werror=array-bounds]
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:676:18: error: array subscript is above array bounds [-Werror=array-bounds]
if (p->msgq_in[j] == pos)
^
/home/thomas/projects/dpdk/dpdk/examples/ip_pipeline/app.h:782:19: error: array subscript is above array bounds [-Werror=array-bounds]
if (p->msgq_out[j] == pos)
^
next prev parent reply other threads:[~2015-07-02 11:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 14:38 [dpdk-dev] [PATCH v3 00/11] ip_pipeline: ip_pipeline application enhancements Maciej Gajdzica
2015-06-29 14:38 ` [dpdk-dev] [PATCH v3 01/11] ip_pipeline: add parsing for config files with new syntax Maciej Gajdzica
2015-06-29 14:38 ` [dpdk-dev] [PATCH v3 02/11] ip_pipeline: added config checks Maciej Gajdzica
2015-07-02 10:14 ` Thomas Monjalon
2015-07-02 10:28 ` Gajdzica, MaciejX T
2015-07-02 11:44 ` Thomas Monjalon [this message]
2015-06-29 14:38 ` [dpdk-dev] [PATCH v3 03/11] ip_pipeline: modified init to match new params struct Maciej Gajdzica
2015-06-29 14:38 ` [dpdk-dev] [PATCH v3 04/11] ip_pipeline: moved pipelines to separate folder Maciej Gajdzica
2015-06-29 14:38 ` [dpdk-dev] [PATCH v3 05/11] ip_pipeline: added master pipeline Maciej Gajdzica
2015-06-29 14:38 ` [dpdk-dev] [PATCH v3 06/11] ip_pipeline: added application thread Maciej Gajdzica
2015-06-29 14:38 ` [dpdk-dev] [PATCH v3 07/11] ip_pipeline: moved config files to separate folder Maciej Gajdzica
2015-06-29 14:38 ` [dpdk-dev] [PATCH v3 08/11] ip_pipeline: added new implementation of passthrough pipeline Maciej Gajdzica
2015-06-29 14:38 ` [dpdk-dev] [PATCH v3 09/11] ip_pipeline: added new implementation of firewall pipeline Maciej Gajdzica
2015-06-29 14:39 ` [dpdk-dev] [PATCH v3 10/11] ip_pipeline: added new implementation of routing pipeline Maciej Gajdzica
2015-06-29 14:39 ` [dpdk-dev] [PATCH v3 11/11] ip_pipeline: added new implementation of flow classification pipeline Maciej Gajdzica
2015-06-29 15:21 ` [dpdk-dev] [PATCH v3 00/11] ip_pipeline: ip_pipeline application enhancements Dumitrescu, Cristian
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=2202302.jFYeIEhALS@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=maciejx.t.gajdzica@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).