DPDK CI discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: David Marchand <david.marchand@redhat.com>, David Liu <dliu@iol.unh.edu>
Cc: "ci@dpdk.org" <ci@dpdk.org>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
	"Pavan Nikhilesh Bhagavatula" <pbhagavatula@marvell.com>
Subject: Re: [dpdk-ci] [EXT] Re: Fedora Rawhide Error on Compile DPDK with GCC11
Date: Thu, 15 Oct 2020 17:17:21 +0000	[thread overview]
Message-ID: <BYAPR18MB2424299A7322ACBFEE4F150CC8020@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8xsvBdfm-W35sQR6TwFzMNL3DdcGbaiwU9n-fGKqDaHXg@mail.gmail.com>


> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, October 15, 2020 10:42 PM
> To: David Liu <dliu@iol.unh.edu>
> Cc: ci@dpdk.org; Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Yigit, Ferruh
> <ferruh.yigit@intel.com>
> Subject: [EXT] Re: [dpdk-ci] Fedora Rawhide Error on Compile DPDK with
> GCC11
> 
> External Email
> 
> ----------------------------------------------------------------------
> On Thu, Oct 15, 2020 at 7:04 PM David Liu <dliu@iol.unh.edu> wrote:
> >
> > Hello everyone,
> >
> > We have successfully added GCC11 to Fedora Rawhide, but when we are
> trying to compile DPDK with GCC11. The compilation failed on an error showed
> below:
> >
> > ../app/test/test_graph_perf.c
> > ../app/test/test_graph_perf.c: In function ‘graph_init’:
> > ../app/test/test_graph_perf.c:311:1: error: wrong number of arguments
> specified for ‘access’ attribute
> >   311 | {
> >       | ^
> > ../app/test/test_graph_perf.c:311:1: note: expected between 1 and 3,
> > found 4 [2368/2483] Compiling C object
> > drivers/libtmp_rte_pmd_octeontx2_event.a.p/event_octeontx2_otx2_worker
> > _dual.c.o
> > ninja: build stopped: subcommand failed.
> >
> > Here is the link to the Bugzilla ticket for this issue:
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.dpdk.org_sho
> > w-5Fbug.cgi-3Fid-3D557-
> 23c0&d=DwIFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=1DGob4
> >
> H4rxz6H8uITozGOCa0s5f4wCNtTa4UUKvcsvI&m=w0Xxi9SSVyT7SSeTovqRzTNxJ
> sdSJD
> > THAI8-EKdfOQM&s=Hv6Fnc9mdcq4GmT8m1OsSbi5tyd_SkFnUeI91ZdSSqI&e=
> 
> Thanks for reporting David.
> I assigned the bz to Jerin, as this is graph unit test code.

We will look into this

> 
> Fyi, we had a couple of gcc 11 fixes from Ferruh and others, but all of them did
> not reach the main tree yet.

Could you share those patches though dome form, So that we can just focus on Graph issue only.

> 
> 
> --
> David Marchand


  reply	other threads:[~2020-10-15 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 17:03 [dpdk-ci] " David Liu
2020-10-15 17:12 ` David Marchand
2020-10-15 17:17   ` Jerin Jacob Kollanukkaran [this message]
2020-10-15 19:17     ` [dpdk-ci] [EXT] " David Marchand

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=BYAPR18MB2424299A7322ACBFEE4F150CC8020@BYAPR18MB2424.namprd18.prod.outlook.com \
    --to=jerinj@marvell.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dliu@iol.unh.edu \
    --cc=ferruh.yigit@intel.com \
    --cc=kirankumark@marvell.com \
    --cc=pbhagavatula@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).