From: Thomas Monjalon <thomas@monjalon.net>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.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, nd <nd@arm.com>
Subject: Re: [dpdk-dev] time for compiling test_ring.c
Date: Wed, 22 Apr 2020 02:25:30 +0200 [thread overview]
Message-ID: <6507321.18pcnM708K@thomas> (raw)
In-Reply-To: <DBBPR08MB4646F8582EE1E2710FE8DD6298D20@DBBPR08MB4646.eurprd08.prod.outlook.com>
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.
> 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 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 0:00 [dpdk-dev] time for compiling test_ring.c Thomas Monjalon
2020-04-22 0:05 ` Honnappa Nagarahalli
2020-04-22 0:25 ` Thomas Monjalon [this message]
2020-04-22 0:32 ` Honnappa Nagarahalli
2020-04-22 5:11 ` Honnappa Nagarahalli
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=6507321.18pcnM708K@thomas \
--to=thomas@monjalon.net \
--cc=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 \
/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.