From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6DF60A0613 for ; Mon, 23 Sep 2019 09:23:58 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D403E1BE3D; Mon, 23 Sep 2019 09:23:56 +0200 (CEST) Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) by dpdk.org (Postfix) with ESMTP id 7951437A2 for ; Mon, 23 Sep 2019 09:23:55 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 7F4511D7E; Mon, 23 Sep 2019 03:23:54 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 23 Sep 2019 03:23:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=ZabCrI932tRIlAkF2CkzFgo11/0eRy5cuBC2GRozJWM=; b=lCGKhNgxt6m+ +AJaIVyGqoI64+BxawyKIBWoyFtyVrjCU60UdAdWsr2SXsAqxORQ5DPK0AQnPriy DOTXh8gvjvHQ8tK4R1HiexXLw4Z4upKJt+eFMFiJ5mzQVZxeUPCJ1xCmiTunOgOf cXjdcsMtSyj/EOp2Z5NVNENbUTfuK9g= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=ZabCrI932tRIlAkF2CkzFgo11/0eRy5cuBC2GRozJ WM=; b=bBVXNvp52R5KXlRLDU4xUZry2BhYqliVVAUcp00N2sIaH0Pnw+aBMaOBE NbVwFfxkz5DBLzZ6d/JYgxvVe5l/Xc/4kgY+jWzSSWB/G97to3Es35YFbKtRdA4L Ap5KcsyWObNpiV4Z4XzMZ8aXOcVkCgLB4dC44Eidl9h/iMgCc7MJ5zXBmrz0onn2 8r4jBQ2N4qO6gMyzAKmjfVmfeFRSXvWzcHude4g3auoI0BnhP2IH0970hTlITNGV N3SDCKnv2joI0t5NrPSVGNcPuhYPJc1m6fScpoA1xzoCrr+l5w1nmmqLpApXxNlo ds4/9cWfhqoeze3EIuFhsgCevKhBA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvdejgdduvddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeelfedrvdefrddutdejrdekkeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhm rghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (88.107.23.93.rev.sfr.net [93.23.107.88]) by mail.messagingengine.com (Postfix) with ESMTPA id 9E802D60062; Mon, 23 Sep 2019 03:23:50 -0400 (EDT) From: Thomas Monjalon To: Ray Kinsella Cc: Bruce Richardson , Andrzej Ostruszka , dev@dpdk.org, Aaron Conole , Michael Santana , John McNamara , Marko Kovacevic , David Hunt , Vladimir Medvedkin , Robert Sanford , Erik Gabriel Carrillo , mattias.ronnblom@ericsson.com, stephen@networkplumber.org, Andrzej Ostruszka Date: Mon, 23 Sep 2019 09:23:47 +0200 Message-ID: <1873473.QF300kEeir@xps> In-Reply-To: References: <20190917075754.8310-1-amo@semihalf.com> <20190919151624.GA1999@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 01/10] build: add an option to enable LTO build X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 20/09/2019 09:38, Ray Kinsella: > > On 19/09/2019 16:16, Bruce Richardson wrote: > > On Thu, Sep 19, 2019 at 02:28:04PM +0100, Ray Kinsella wrote: > >> > >> > >> On 19/09/2019 13:35, Andrzej Ostruszka wrote: > >>> On 9/18/19 3:32 PM, Ray Kinsella wrote: > >> ...> > >>> Compilation time is much longer. In a normal hack|fix/compile/repeat > >>> cycle with "compile" part being simple "make" the link time might be a > >>> bit annoying. So I imagine keeping LTO off for the most part of the dev > >>> cycle and then at the end when doing release/cleanup turn LTO on - to > >>> either get release build ready or to get some set of warnings that you > >>> address before yet another attempt to release build. > >> > >> Well look, I would say a few things. > >> > >> 1. I see build times going down dramatically with Meson/Ninja in any case. > > > > In the general case yes, but mainly it helps if you have a large number of > > cores. For anyone building in a CI with only a couple of cores, meson+ninja > > isn't going to help much. > > > > /Bruce > > > > Very true, and I completely acknowledge that LTO adds compilation time. > I would just like to see it in or out, not another build time option. Please can we get some numbers to understand how longer it is?