From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9EC27A00C5; Tue, 21 Jun 2022 13:53:38 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 495C54069C; Tue, 21 Jun 2022 13:53:38 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id 1939040151 for ; Tue, 21 Jun 2022 13:53:37 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 5E87E5C0091; Tue, 21 Jun 2022 07:53:35 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 21 Jun 2022 07:53:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1655812415; x= 1655898815; bh=C6WWXY8mA730e2DTG6P9JiliXUqm6TYpYvncI5E0C3w=; b=H t2WLSLIVDV6a4rwU6tS6OET0OGfkof1JfH3VSLkRsMY3yZL/gbJ+vYPxplg80lKi 0itHDx5oJbNI/Ftx5d5CZ7eI6+Kae4EiiTgSlcjQeUr8ABD61NkS6S2OgmSUVQfh ttS2o6Mdr2Q1QGxK2SDaqTC9xHK3eAZ7e7bGT9+0m2PGewKV+oUl3UzKllqgZwW+ tg8hGSn8LPW7sJiad0oDRfPMWlOQVCi9p9UiaZJ1NBLkpyKjJmiK/p8QlloOqbVk S4YAwZn8YyYhxDm4qVSBusCFN/pG4igVC13YQBHi0TU5DWuNZHItuJo+SaQC83ae MXvmz5YNAi8k8SSeKU22Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1655812415; x= 1655898815; bh=C6WWXY8mA730e2DTG6P9JiliXUqm6TYpYvncI5E0C3w=; b=l K7ryF3Q+oD9Wi759WP42rN98qckzvKcrZLUT+00n7mFzbwkIucKN9i8LYqzu3SY0 rE0FzRP7Mbgg+7CA1TRofbAKvaGj3LJblywG211/+caCawfbrhNiV0XI8RzDxsjT wKs8ScZzzkXSfDiQJ56ZTxnfkMv0PF+5G3r7qKX7nm9HekxMXWGcdbcB0MVUH7RU oMcpFKo1FTxSGAAZ4XnCpb8/PjdFa6+zm0eNikgdx4N/0uMIo1Nnqo/71OKO5Vw2 DARlq45zT5yFOc7cSbvEoFnArCtLq/GvGAhYyvz1KkFLQaZQ66CkfffcEk3XqSgr b5g49rrwlrfvN0ngpll4g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudeffedggeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthhqredttddtjeenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpeegtddtleejjeegffekkeektdejvedtheevtdekiedvueeuvdei uddvleevjeeujeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 21 Jun 2022 07:53:33 -0400 (EDT) From: Thomas Monjalon To: =?utf-8?B?U3RhbmlzxYJhdw==?= Kardach Cc: Bruce Richardson , David Christensen , David Marchand , dev , upstream@semihalf.com, Aaron Conole , "Ananyev, Konstantin" , "Ruifeng Wang (Arm Technology China)" , Jerin Jacob Kollanukkaran Subject: Re: [PATCH 0/3] Fix xmm_t to rte_xmm_t scalar conversion Date: Tue, 21 Jun 2022 13:53:32 +0200 Message-ID: <3457544.ZfL8zNpBrT@thomas> In-Reply-To: References: <20220609121701.716299-1-kda@semihalf.com> <4127934.SvYEEZNnvj@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 21/06/2022 13:05, Stanis=C5=82aw Kardach: > On Tue, Jun 21, 2022 at 12:22 PM Thomas Monjalon wr= ote: > > > > 21/06/2022 11:49, Bruce Richardson: > > > On Tue, Jun 21, 2022 at 11:42:55AM +0200, Stanis=C5=82aw Kardach wrot= e: > > > > On Tue, Jun 21, 2022 at 11:39 AM Bruce Richardson > > > > wrote: > > > > > > > > > > Generally the "cpp" binary is not the c-plus-plus one, but the C > > > > > preprocessor one. Perhaps the original files are incorrect here, = and should > > > > > all refer to g++. > > > > > > > > > > /Bruce > > > > > > > > > That does make sense. I'll submit a separate patchset fixing all > > > > occurrences (of which there are many). > > > > > > > > > > As a more general note for future consideration, I notice that in mes= on > > > 0.56 the cross-file support has been enhanced with the ability to use > > > constants and therefore separate out prefixes.[1] > > > > > > When we get to the point where we feel we can mandate meson 0.56 upwa= rds > > > for cross compilation, we should look to leverage this. It should even > > > allow other scripts such as test-meson-builds to auto-generate the co= nstant > > > paths to the binaries on the fly, effectively allowing the use of > > > environment variables for these - something previously requested by T= homas. > > > > That would be great. > > Cross compilation prefix is such a basic thing, we should handle it pro= perly. > Please correct me if I'm wrong but it seems that meson's approach to > cross-compiling is to package all settings into cross-files. Probably > under assumption that a repeatable compilation is more important than > flexibility and that there are compiler-specific knobs that need/can > to be tuned. Therefore reading CROSS_COMPILE/prefix from environment > is intentionally made hard. If it is made intentionally hard, it is just a wrong design. A toolchain prefix is just a name. We can have 2 toolchains compiled with the same name and different behaviou= rs. And we can have 2 similar toolchains with a different name. > So should the direction be environment or rather separating > cross-files into arch-part and toolchain-parts and letting user create > his own toolchain part while maintaining a matrix of supported > combinations for CI? I'm not advocating either, just want to wrap my > head around it. We should be able to use a toolchain compiled anywhere without modifying the cross files, just because a "-gnu-" is missing or any other irrelevant detail.