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 69CD74C74 for ; Mon, 5 Nov 2018 15:15:57 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B752E21B42; Mon, 5 Nov 2018 09:15:56 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 05 Nov 2018 09:15:56 -0500 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=WwPJkYjo7zd/CBRH8jtk6dsknXaV+jsjfNA1QxAs8ac=; b=Lh1J27Fcwyco AoFd0XA5NIccjeDCMfyHijV7h/k9F6zHMQ705jxvFYR2PGv8Z6qkdRvFUrMW3gGI +g9LuiW8xpkXBoLdJbz6gFeMtH1N6iUn2Gnac2lkMJSa8N34C63A0Om3hg5rpOIR GY+BwaFGOKwCY4Fd+qd6/qVM7Idy9YM= 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=fm1; bh=WwPJkYjo7zd/CBRH8jtk6dsknXaV+jsjfNA1QxAs8 ac=; b=KiJxYJii0F//FBFZ/Z6wCZHo/IelsxRc8G3ACKR3GbcvZ5X/ODdqfzHYF TXW3GFs5twwPwtRr+9uc4c/GfTb+pMkVHnWjHv9iqXNlcTiKxEP1ejx1MAhCalzC PlgfgjAzOiNtxtzvdZdxneyhahh9a9tkqNLHNf8uSzjPyj3v5xaDMLZo3lGETEuT hnqAWQVzUC5QzBaW23oEQYwIhSPtTwVZZpIObOj0PrlX2mGuLRHa6MJPDG0TjZq/ 4rCAL1cvoh5bS9p1i/Ics2l2g+0nCLf8iIAVFrFyqOvBNMl43dG7N7Y50cwMLl6s 2Bxfh46oubARVEL6H6DDIIYy9plpw== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 5A70FE47C4; Mon, 5 Nov 2018 09:15:54 -0500 (EST) From: Thomas Monjalon To: Christian Ehrhardt Cc: dev@dpdk.org, TYOS@jp.ibm.com, adrien.mazarguil@6wind.com, Gowrishankar Muthukrishnan , Chao Zhu , Luca Boccassi , Pradeep Satyanarayana , dwilder@us.ibm.com Date: Mon, 05 Nov 2018 15:15:53 +0100 Message-ID: <2547699.pxo2WhrkVo@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] ppc64: fix compilation of when AltiVec is enabled 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: Mon, 05 Nov 2018 14:15:57 -0000 Hi, 30/08/2018 13:58, Christian Ehrhardt: > On Thu, Aug 30, 2018 at 12:52 PM Takeshi T Yoshimura > wrote: > > Hi, > > I could reproduce the issue you reported in 18.08 with my ppc64le box with > > RedHat 7.5 and GCC4.8. > > The patch resolved the issue in my environment. Thanks! > > I added your test (tanks) and Adrien's extensive review/discussion as tags > and also addressed a few checkpatch findings. > V2 is up on the list now ... > > > I am a bit newbie in dpdk-dev, but I will try contacting Chao and other > > IBM guys... Sorry for our slow reply. > > Thanks for your participation Takeshi, > we at least now have had a few replies after Thomas used the superpowers of > "CPT. CAPSLOCK" \o/. > > I also have a call later today to make sure this is brought up inside IBM > to make sure someone is maintaining it for real. Summary of the situation: - I used caps lock on August 30th - We got replies on the ML in the next 2 days (Alfredo, Chao, Takeshi) - On September 3rd, Adrien raised a major issue for C++ with the fix v3 http://mails.dpdk.org/archives/dev/2018-September/110733.html - Another email about a possible GCC fix on September 5th (David Wilder) - There was a private reply on September 27th, confirming an IBM support - and nothing else Nobody at IBM requests to get a compilation fix for ppc64. And there was no issue raised after 18.11-rc1 release. I guess it means DPDK is not used on ppc64. In this case, we should mark the ppc port as unmaintained for 18.11. OR SHOULD I USE MY CAPS LOCK AGAIN?