From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: olivier.matz@6wind.com, david.marchand@redhat.com,
bruce.richardson@intel.com, dev@dpdk.org
Subject: [dpdk-dev] time for compiling test_ring.c
Date: Wed, 22 Apr 2020 02:00:31 +0200 [thread overview]
Message-ID: <6060324.K2JlShyGXD@thomas> (raw)
Hi,
I don't want know why and when, but it seems the file test_ring.c
became very long to compile, especially with clang.
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 :-(
next reply other threads:[~2020-04-22 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 0:00 Thomas Monjalon [this message]
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
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=6060324.K2JlShyGXD@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=konstantin.ananyev@intel.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 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).