From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: "olivier.matz@6wind.com" <olivier.matz@6wind.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>, nd <nd@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] time for compiling test_ring.c
Date: Wed, 22 Apr 2020 05:11:02 +0000 [thread overview]
Message-ID: <DBBPR08MB4646007CC463697558A407D098D20@DBBPR08MB4646.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <DBBPR08MB46460EC50E61168363F37C4898D20@DBBPR08MB4646.eurprd08.prod.outlook.com>
<snip>
>
> >
> > 22/04/2020 02:05, Honnappa Nagarahalli:
> > > 22/04/2020 02:00, Thomas Monjalon:
> > > > I don't want know why and when, but it seems the file test_ring.c
> > > > became very long to compile, especially with clang.
> > >
> > > What is the compiler version? Is this on master?
> >
> > clang 9.0.1 compiling DPDK master.
> I think, it is the compiler. The issues were observed with clang-7 during the last
> release. Clang-8 worked fine. Still, test_ring.c was re-worked to compile in
> shorter time. Looks like things are back to broken in 9.0.1.
I am able to reproduce, need sometime to come up with a fix.
>
> >
> > > Any info on test_ring_perf.c?
> >
> > This one looks slow to compile as well.
> >
> > > > I have no solution to shorten the compilation time, so I propose
> > > > to rename test_ring.c to test_patien.ce.
> > > > Disclosure: I am failing this test :-(
> >
> > The object file takes 5 to 11MB.
> > I don't know how much this test is magic, but I hope it does a lot
> > more than this 256B program:
> > https://www.youtube.com/watch?v=Imquk_3oFf4
> >
next prev parent reply other threads:[~2020-04-22 5:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 0:00 Thomas Monjalon
2020-04-22 0:05 ` Honnappa Nagarahalli
2020-04-22 0:25 ` Thomas Monjalon
2020-04-22 0:32 ` Honnappa Nagarahalli
2020-04-22 5:11 ` Honnappa Nagarahalli [this message]
2020-04-22 8:12 ` Thomas Monjalon
2020-04-22 14:23 ` Wiles, Keith
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=DBBPR08MB4646007CC463697558A407D098D20@DBBPR08MB4646.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=olivier.matz@6wind.com \
--cc=thomas@monjalon.net \
/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).