From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 361AF1C691 for ; Wed, 4 Apr 2018 16:31:58 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B0CCD211E0; Wed, 4 Apr 2018 10:31:57 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 04 Apr 2018 10:31:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=Wft9XiRlY1RvFbgizbdBiFWUFg rM3XRSQNBkf2LUiNM=; b=V38H/fJkcJAtdMi6cueb8fh9tNT5a9SqIWxWqzUYcc P4dOTE0RCB9Ux8w2+r9VlhA9GGn9sRYJ8cD/WjRt8eXGwmXWaAdtXg/Z2+ht50NF FtPKanuoLhR+HOVyBtRf2vzrwdQUBsE2N66p7/k8I8Yv8230raVeE9t9hvwwuGF4 g= 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-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Wft9Xi RlY1RvFbgizbdBiFWUFgrM3XRSQNBkf2LUiNM=; b=nYPAgyf46dp804wlhBAwT5 x9rS3vRjxmi0/q8GPZxfr6s7Ar7X09hb9Y9jDVql1o2wr81bKER0JKdnHIspJi3w LMW1GPqClftXCgSZnt43V0B+4U9j9LHc+TV4rrU7ncfUrky6d574E3LkRfoWgZIa LG/3lsKUCvXTzRsT/mFZhgX/Cn3LZxq7VK6wxz3pam8Y7ZmYUDMEKBC1P4Ujg9ld /f/U2/1sNguyaDf7QSO6OslzGllbpg9ouXreOVDQ8bMJ5T+voejs7KbrGjF3eTSv Zyd2t3u+GmolhPdEr1nrAGx4uIrkFTPV3542FP4P6KtoeyVZ5cQjf2TqerIstjug == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 1BF73E43C8; Wed, 4 Apr 2018 10:31:57 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org, pablo.de.lara.guarch@intel.com Date: Wed, 04 Apr 2018 16:31:55 +0200 Message-ID: <2469243.8txvrLPoSt@xps> In-Reply-To: <20180329093924.1984d7f4@xeon-e3> References: <20180329093924.1984d7f4@xeon-e3> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [BUG] cuckoo_hash build failure with gcc-8 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: , X-List-Received-Date: Wed, 04 Apr 2018 14:31:58 -0000 +Cc Pablo 29/03/2018 18:39, Stephen Hemminger: > Cuckoo hash has build failure with gcc-8. > The casting here is suspect anyway. It should be fixed more directly. >=20 > CC rte_table_hash_cuckoo.o > lib/librte_table/rte_table_hash_cuckoo.c: In function =E2=80=98rte_table_= hash_cuckoo_create=E2=80=99: > lib/librte_table/rte_table_hash_cuckoo.c:110:16: error: cast between inco= mpatible function types from =E2=80=98rte_table_hash_op_hash=E2=80=99 {aka = =E2=80=98long unsigned int (*)(void *, void *, unsigned int, long unsigned= int)=E2=80=99} to =E2=80=98uint32_t (*)(const void *, uint32_t, uint32_t)= =E2=80=99 {aka =E2=80=98unsigned int (*)(const void *, unsigned int, unsig= ned int)=E2=80=99} [-Werror=3Dcast-function-type] > .hash_func =3D (rte_hash_function)(p->f_hash), > ^ > cc1: all warnings being treated as errors