From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mk: use icc default inline limit
Date: Thu, 30 Mar 2017 22:35:31 +0200 [thread overview]
Message-ID: <2005254.o1hyILMhH9@xps13> (raw)
In-Reply-To: <20170327143544.9498-1-ferruh.yigit@intel.com>
2017-03-27 15:35, Ferruh Yigit:
> ICC build time
> Before this patch (bnx2x PMD enabled [1])
> real 8m16.622s
>
> After this patch (bnx2x enabled)
> real 0m35.140s
>
> [1]
> bnx2x cause the build take a lot, otherwise build times are more sane
> numbers.
>
> ICC has a default inline limit and when this limit is hit it generates
> a warning, and in DPDK this breaks the build.
>
> Previous solution was to remove the inline limit, which does more
> aggressive inlining and build may take too much time.
>
> This patch keeps the default inline limits, but prevents the warning ICC
> generates.
>
> Fixes: 8acbad88c4fa ("mk: fix build with icc-15")
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks
prev parent reply other threads:[~2017-03-30 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 14:35 Ferruh Yigit
2017-03-30 20:35 ` Thomas Monjalon [this message]
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=2005254.o1hyILMhH9@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).