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 E334714EC for ; Wed, 7 Nov 2018 11:03:33 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5F9B92229F; Wed, 7 Nov 2018 05:03:33 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 07 Nov 2018 05:03:33 -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=Fqb9VswEQv17Y70+mrML0UnIqkxoxg4vNbxAsaj/ks4=; b=k6HMqnH+vGWD XMi5GU37Kdg/fq79/W7fuxaDuejFBwt7g6ymUgSeS5Ms5Ffv7EzkynJk5LEGugSd Idy3eEs1nW/MgfmFJ521uE4kZm1n1cNA/MuLROk/GhYHffdgIala63YpXh0yCV0N PO+AHsPp3oIUSJYycMLK8BsaJpjRL6w= 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=Fqb9VswEQv17Y70+mrML0UnIqkxoxg4vNbxAsaj/k s4=; b=YtCTlH5pxJBZKa6eBPmq1f2o5ruEed5T5hWfIFHwdNuRlqDjGBzQeHOvI /BTm45HKl+iV/n1DC64kMtShq1Az1pFHpf5ud+7YlDe38uGc3pLuDbexPTLQ1p69 Zv5dZmK37n7yuk6a7alnC2fHQAhgLc7Xizp+ZZRA/zUpLQ3M9Fe8wSio3M8DV5ro IVywNH9I0fQJ0H7N7xt5XNiHX3t50esHlILJuRxuCJqXtuYx2IYybt/hGeghPmk3 ev/CLTVIP6YFYXgk0cEMXwWjF8lp1MQNX2SSM2TB+FLHRrXRjSjtSP62YSUGB2GL 9H5yOXXuBq2l0j3I3qrbifcXfXN9w== 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 878E2102A0; Wed, 7 Nov 2018 05:03:31 -0500 (EST) From: Thomas Monjalon To: Pradeep Satyanarayana Cc: dev@dpdk.org, adrien.mazarguil@6wind.com, Luca Boccassi , Chao Zhu , Christian Ehrhardt , dwilder@us.ibm.com, TYOS@jp.ibm.com Date: Wed, 07 Nov 2018 11:03:30 +0100 Message-ID: <8589266.XCptXWt5vM@xps> In-Reply-To: References: <2547699.pxo2WhrkVo@xps> 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: Wed, 07 Nov 2018 10:03:34 -0000 05/11/2018 22:20, Pradeep Satyanarayana: > From: Thomas Monjalon > > 30/08/2018 13:58, Christian Ehrhardt: > > > On Thu, Aug 30, 2018 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) > > As Dave mentioned that is only expected in GCC 9. > > > - 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. > > Yes, we do need fixes for ppc64. > > (1) http://mails.dpdk.org/archives/dev/2018-August/110499.html > (2) http://mails.dpdk.org/archives/dev/2018-September/110961.html > > Based on the above 2 URLs (tested both by Takeshi and David Wiler), we > assumed that it would get picked up in 18.11. > We have been more focussed on 17.11 (and likely dropped > the ball on 18.11) > since 17.11 is an LTS release and we have had lots of problems on ppc64. Note that 18.11 is also LTS. > Should be submitting patch to fix those issues shortly. Sorry, I have some doubts for two reasons: - track records - technical reality: there is no perfect solution outside of GCC > We have built 18.11-rc1 with the fix above (1), and it does work on > ppc64le. But it would break C++ applications. > An updated version of: > > (3) http://mails.dpdk.org/archives/dev/2018-August/109926.html > > also builds on ppc64. The latter has the advantage of possibly not > breaking existing applications. But it fixes only mlx5. stdbool is used in many other places. Which PMDs are you compiling? Are you compiling examples? > > 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? > > Thanks for your patience while we iron out the issues. > Hopefully, we don't need the CAPS LOCK again. We have to mention the ppc64 incompatibility in 18.11 release notes. Either it stays as is and we declare DPDK 18.11 not supported on IBM platforms, or we fix it and document the limitations.