From: David Marchand <david.marchand@redhat.com>
To: Jerin Jacob <jerinjacobk@gmail.com>
Cc: taox.zhu@intel.com, Jerin Jacob <jerinj@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Vamsi Attunuru <vattunuru@marvell.com>, dpdk-dev <dev@dpdk.org>,
Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-dev] [PATCH] mempool/octeontx2: fix compile issue
Date: Mon, 17 Feb 2020 15:57:25 +0100 [thread overview]
Message-ID: <CAJFAV8x1jXF8U3ZmgyK8tNecj_Bv=5mXkd9_vcMLHY=3P6S+PA@mail.gmail.com> (raw)
In-Reply-To: <CALBAE1OxfirViEC0-Y6=DbQ63nr9rTLWLdPUry7jq7jgUPpA5A@mail.gmail.com>
On Mon, Feb 17, 2020 at 2:06 PM Jerin Jacob <jerinjacobk@gmail.com> wrote:
>
> On Mon, Feb 17, 2020 at 1:39 PM <taox.zhu@intel.com> wrote:
> >
> > From: Tao Zhu <taox.zhu@intel.com>
> >
> > Change the definition of C99 style to C90 style.
> > compile log as below:
> >
> > otx2_mempool_ops.c: In function ‘otx2_npa_populate’:
> > /dpdk/drivers/mempool/octeontx2/otx2_mempool_ops.c:790:2: error: \
> > ‘for’ loop initial declarations are only allowed in C99 mode
> > for (int i = 0; i < OTX2_L1D_NB_SETS; i++)
> > ^
> > /dpdk/drivers/mempool/octeontx2/otx2_mempool_ops.c:790:2: \
> > note: use option -std=c99 or -std=gnu99 to compile your code
> > /dpdk/drivers/mempool/octeontx2/otx2_mempool_ops.c: At top level:
> > cc1: error: unrecognized command line option \
> > "-Wno-address-of-packed-member" [-Werror]
> > cc1: all warnings being treated as errors
> > make[6]: *** [otx2_mempool_ops.o] Error 1
> > make[5]: *** [octeontx2] Error 2
> > make[4]: *** [mempool] Error 2
> >
> > Fixes: 9ed8e95c ("mempool/octeontx2: optimize for L1D cache architecture")
> >
> > Signed-off-by: Tao Zhu <taox.zhu@intel.com>
>
> Just for understanding purposes, Why one need to use C90 instead of
> C99? May I know, What environment, Do you see this issue?
> In any case,
>
> Reviewed-by: Jerin Jacob <jerinj@marvell.com>
We can see this in RHEL/Centos 7 and SLE 12 (thanks Luca).
--
David Marchand
next prev parent reply other threads:[~2020-02-17 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:43 taox.zhu
2020-02-17 11:19 ` David Marchand
2020-02-17 14:57 ` David Marchand
2020-02-17 18:04 ` Jeremy Plsek
2020-02-17 18:28 ` Thomas Monjalon
2020-02-17 13:06 ` Jerin Jacob
2020-02-17 14:57 ` David Marchand [this message]
2020-02-17 18:29 ` 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='CAJFAV8x1jXF8U3ZmgyK8tNecj_Bv=5mXkd9_vcMLHY=3P6S+PA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=ndabilpuram@marvell.com \
--cc=taox.zhu@intel.com \
--cc=vattunuru@marvell.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).