From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f171.google.com (mail-pf0-f171.google.com [209.85.192.171]) by dpdk.org (Postfix) with ESMTP id 81D1A1041 for ; Fri, 8 Sep 2017 21:08:17 +0200 (CEST) Received: by mail-pf0-f171.google.com with SMTP id y29so5092440pff.0 for ; Fri, 08 Sep 2017 12:08:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=O4qSvFuq/3HYqRLVesamQ0kkBd9gakcEs5tH5So/dls=; b=15LGxQzeWIaz8DBvm1u/DUOC+WH2ZTMMIDJ4rVT/x8JPTLkPzRXCjux4FdhioHN4TC 2y5G4+TLX7hIzwiFLS/EXEiNGyK7XR+dbU5n3aLcEBuGvc0PyYRc0x07JyL85cNEi6bG I44i6fJEVAjQAKh2V1kMw3s1fkxu+voYmqgBzyzXO7tORzfpgHgwzaIirObNpTFQxB+x riMfBfnMfJMGxHAy3xjFepoFG3SvCuZRXirpjMUuU5Xx+V+8eD6ca1gWOyCj9XVVBeZQ bFLlm60i8/1mkSdsROnMv1cHKcN4rtwKtYGAfsBLx54A7TN/KADDU+HLapLic1KWERX/ 7S5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=O4qSvFuq/3HYqRLVesamQ0kkBd9gakcEs5tH5So/dls=; b=eKlRmTbbcMRLgqi5EFDCSgGH2C5GWOFqdPrG4moTm0Qg3vPMAH33CjKpblKTvyy4x0 UtKfENuyo6sZRHcXdFR0sNIOjrdLr8x1KnWFl1O4OJc13kDjlns0JXKc4b3jTUlJvW99 Uz4q0YTMuzdzlBwvlsKXTg71Olp3oDFi5KewSJzAe+Z7VRCrtvfntJundsfwT9v4WAK9 WHtNH3n1D3vVxQC7WCHN9cnCUjyDM3C+uDSS65FZKCZfhmOYsS/BZdzZWUW63CXS+NOy m1Ln91WicxSDwuxcOXsNu5pcg7XBGShBdAxo2YN3LnWuas1uHgmYDTpvISjcDnnFKgDe QHag== X-Gm-Message-State: AHPjjUgonoQoQLtApZZlKODjwqrGjqlV8BRrRW0iPHDFg7mCWz5yCp23 +AxRN9yTGW/ToEEQz5TeCg== X-Google-Smtp-Source: ADKCNb7clga3d/IGbZ6mzqCT2ooNJL3ahBfaB7SM9mGvWf1CtgmEdeYnwv1uah6duQrH8Za9hs+Wrg== X-Received: by 10.98.65.27 with SMTP id o27mr4157080pfa.205.1504897696763; Fri, 08 Sep 2017 12:08:16 -0700 (PDT) Received: from xeon-e3 (76-14-207-240.or.wavecable.com. [76.14.207.240]) by smtp.gmail.com with ESMTPSA id 85sm5082863pfk.64.2017.09.08.12.08.16 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 08 Sep 2017 12:08:16 -0700 (PDT) Date: Fri, 8 Sep 2017 12:08:14 -0700 From: Stephen Hemminger To: Yuyong Zhang Cc: "users@dpdk.org" Message-ID: <20170908120814.6c515149@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-users] compile warning in dpdk lib header files "error: inlining failed in call .... call is unlikely and code size would grow" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Sep 2017 19:08:17 -0000 On Fri, 8 Sep 2017 18:45:52 +0000 Yuyong Zhang wrote: > Hi, >=20 >=20 >=20 > I got lots of compile warning when integrating dpdk library such as: >=20 >=20 >=20 > : error: inlining failed in call to =E2=80=98rte_mempool_ops_dequeue_bulk= .part.1=E2=80=99: call is unlikely and code size would grow [-Werror=3Dinli= ne] >=20 >=20 >=20 > : error: inlining failed in call to =E2=80=98rte_pktmbuf_free": call is u= nlikely and code size would grow [-Werror=3Dinline] >=20 >=20 >=20 > 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 unlik= ely branchs.