From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 40215A0093; Tue, 3 May 2022 14:30:21 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D9A0840C35; Tue, 3 May 2022 14:30:20 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by mails.dpdk.org (Postfix) with ESMTP id 6F15740691 for <dev@dpdk.org>; Tue, 3 May 2022 14:30:19 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1651581019; x=1683117019; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=K01Y702CBbDkQ5eHDyqTxra5DjkXkJpE4kojNPcCdxI=; b=fp8ll92oL+IkX75hpoeb4s8n/z2uF57QurzhdkiGmIGtPOiYMV6E9QgV kSUt9EyOoRXV8GitiWhb+7o9LjCMMlatCwFiqAcIyeQPFzoaeYy8kgpHO aQDvwnJWL6H8vS6QqQtClz0Vdh622emewnpDf2iLBAyiyUWlRFHLFQo1k 337pYV97x2nb8T6qb/xTrObX6GSBZsuSAlhtDmOUFchnHDLYOe6oDmvjz F1QFtcPu8TSgeK55EqJm35cxv47RJmU3mmsnUevSkunfGKczlLRBjXcw7 6oSHkJy3QtWzOIwR1xo8MM6rosNUz/B0hHryHyQZeqNOT2G+jy1ede06o A==; X-IronPort-AV: E=McAfee;i="6400,9594,10335"; a="330452721" X-IronPort-AV: E=Sophos;i="5.91,195,1647327600"; d="scan'208";a="330452721" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 May 2022 05:30:15 -0700 X-IronPort-AV: E=Sophos;i="5.91,195,1647327600"; d="scan'208";a="516549856" Received: from bricha3-mobl.ger.corp.intel.com ([10.55.133.40]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 03 May 2022 05:30:13 -0700 Date: Tue, 3 May 2022 13:30:09 +0100 From: Bruce Richardson <bruce.richardson@intel.com> To: Thomas Monjalon <thomas@monjalon.net> Cc: dev@dpdk.org, David Christensen <drc@linux.vnet.ibm.com>, Beilei Xing <beilei.xing@intel.com>, Matan Azrad <matan@nvidia.com>, Viacheslav Ovsiienko <viacheslavo@nvidia.com>, Maxime Coquelin <maxime.coquelin@redhat.com>, Chenbo Xia <chenbo.xia@intel.com>, Vladimir Medvedkin <vladimir.medvedkin@intel.com> Subject: Re: [PATCH] avoid AltiVec keyword vector Message-ID: <YnEgUSJ77f7+RR4u@bricha3-MOBL.ger.corp.intel.com> References: <20220503120321.2438479-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220503120321.2438479-1-thomas@monjalon.net> X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org On Tue, May 03, 2022 at 02:03:21PM +0200, Thomas Monjalon wrote: > The keyword "vector" may conflict easily. > As a rule, it is better to use the alternative keyword "__vector". > hi Thomas, could you perhaps clarify a bit more in the log, I'm not aware of it being a keyword generally. What would "vector" conflict with? If it's a keyword is it possible to use it as a variable name in these files? Thanks, /Bruce