From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Aaron Conole <aconole@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
Ruifeng Wang <Ruifeng.Wang@arm.com>, nd <nd@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] test/ring: fix long compilation time
Date: Thu, 30 Apr 2020 19:51:37 +0000 [thread overview]
Message-ID: <DBBPR08MB464602032862C1E85C81A20598AA0@DBBPR08MB4646.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <f7tftckewme.fsf@dhcp-25.97.bos.redhat.com>
> > <snip>
> >
> >> Subject: Re: [PATCH] test/ring: fix long compilation time
> >>
> >> Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> writes:
> >>
> >> > test_ring.c takes lot of time to compile with clang. It is
> >> > reproducable with compiler version 8.0 on Ubuntu 18.04.
> >> > Amount of testing is reduced, but attempt is made to keep the same
> >> > coverage.
> >> >
> >> > Reported-by: Aaron Conole <aconole@redhat.com>
> >> > Reported-by: Thomas Monjalon <thomas@monjalon.net>
> >> > Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> >> > Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> >> > ---
> >>
> >> Thanks, Honnappa!
> >>
> >> One thing to note, I don't see this with just clang - it occurs with gcc as
> well.
> >> I'm going to test this patch today.
> > Which gcc version are you using? I do not see test_ring.c taking much
> > time for compilation for gcc on my x86 platform.
>
> 7.4.0, but I'm also adding asan and ubsan to it.
Ok, ubsan+ gcc 8.4.0 is taking time on Arm as well.
>
> > The clang issue is seen on x8, on Arm it does not show issues.
>
> I didn't check arm, yet
next prev parent reply other threads:[~2020-04-30 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 1:56 Honnappa Nagarahalli
2020-04-30 10:23 ` Thomas Monjalon
2020-06-16 12:47 ` Thomas Monjalon
2020-06-25 8:19 ` David Marchand
2020-06-25 11:05 ` Ananyev, Konstantin
2020-07-02 20:42 ` Honnappa Nagarahalli
2020-04-30 12:55 ` Aaron Conole
2020-04-30 16:03 ` Honnappa Nagarahalli
2020-04-30 17:01 ` Aaron Conole
2020-04-30 19:51 ` Honnappa Nagarahalli [this message]
2020-05-01 12:56 ` Aaron Conole
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=DBBPR08MB464602032862C1E85C81A20598AA0@DBBPR08MB4646.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.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).