From: Stephen Hemminger <stephen@networkplumber.org>
To: Yuyong Zhang <yuyong.zhang@casa-systems.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] compile warning in dpdk lib header files "error: inlining failed in call .... call is unlikely and code size would grow"
Date: Fri, 8 Sep 2017 12:08:14 -0700 [thread overview]
Message-ID: <20170908120814.6c515149@xeon-e3> (raw)
In-Reply-To: <BN6PR06MB2756A0BB9A23CB1FB6350242B9950@BN6PR06MB2756.namprd06.prod.outlook.com>
On Fri, 8 Sep 2017 18:45:52 +0000
Yuyong Zhang <yuyong.zhang@casa-systems.com> wrote:
> Hi,
>
>
>
> I got lots of compile warning when integrating dpdk library such as:
>
>
>
> : error: inlining failed in call to ‘rte_mempool_ops_dequeue_bulk.part.1’: call is unlikely and code size would grow [-Werror=inline]
>
>
>
> : error: inlining failed in call to ‘rte_pktmbuf_free": call is unlikely and code size would grow [-Werror=inline]
>
>
>
> Because company policy strictly enforces "waring as error", I have to fix those issues.
Turn off the warning, or fix the policy.
DPDK does lots of inlining and in some cases the code will be used in unlikely branchs.
next prev parent reply other threads:[~2017-09-08 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 18:45 Yuyong Zhang
2017-09-08 19:08 ` Stephen Hemminger [this message]
2017-09-08 19:15 ` Yuyong Zhang
2017-09-08 21:51 ` Stephen Hemminger
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=20170908120814.6c515149@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=users@dpdk.org \
--cc=yuyong.zhang@casa-systems.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).