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 85120A0032; Tue, 21 Jun 2022 11:49:29 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 44022427F1; Tue, 21 Jun 2022 11:49:29 +0200 (CEST) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id E0EF240151 for ; Tue, 21 Jun 2022 11:49:26 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1655804967; x=1687340967; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=SSER3zOcEf/JtUXpTQ0m4WlCAehTg7l8mos1UKOO+j8=; b=hnjpmcEadpQH8uRFolPLPKa8wDG3gUPjiiJoSdzvCD/AnCg9nOxJlH1S Kr5yFqq9xtfjlTS+LDfUHsQOT6cHX9Koe2s93ZNMnSH7jNndDmGDlIiH3 xE2sreuaj8mPDIUCNX6GnxnAuWmUwxB30v8GmaFOHGK+DAkFDi18Wm5cm 7iiMExhRUyjSlYdtCaBau28BiUq7MalCytVi358mZfQoymRQ5wCADkjZR 0uLePNPNTOwdudmm7b6GBZTaP5ceHPNDUGmPoDi0L/zzhzRRk2L4/DUEg 450pfsTRfh0BtPUZ8hDhF3uCLvz+9dFTx1WIvCuktYqdRIHWgTDGL2Bry A==; X-IronPort-AV: E=McAfee;i="6400,9594,10384"; a="281137393" X-IronPort-AV: E=Sophos;i="5.92,209,1650956400"; d="scan'208";a="281137393" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Jun 2022 02:49:22 -0700 X-IronPort-AV: E=Sophos;i="5.92,209,1650956400"; d="scan'208";a="643548787" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.10.248]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 21 Jun 2022 02:49:18 -0700 Date: Tue, 21 Jun 2022 10:49:13 +0100 From: Bruce Richardson To: =?utf-8?Q?Stanis=C5=82aw?= Kardach Cc: David Christensen , David Marchand , dev , upstream@semihalf.com, Aaron Conole , "Ananyev, Konstantin" , "Ruifeng Wang (Arm Technology China)" , Jerin Jacob Kollanukkaran , thomas@monjalon.net Subject: Re: [PATCH 0/3] Fix xmm_t to rte_xmm_t scalar conversion Message-ID: References: <20220609121701.716299-1-kda@semihalf.com> <63ed6e6c-337d-8f8a-9410-1e43b0561967@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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 On Tue, Jun 21, 2022 at 11:42:55AM +0200, Stanisław Kardach wrote: > 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 meson 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 upwards for cross compilation, we should look to leverage this. It should even allow other scripts such as test-meson-builds to auto-generate the constant paths to the binaries on the fly, effectively allowing the use of environment variables for these - something previously requested by Thomas. /Bruce [1] https://mesonbuild.com/Machine-files.html#constants