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 C9C4BA054F; Wed, 25 May 2022 10:19:03 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6FCFE400EF; Wed, 25 May 2022 10:19:03 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id B8F8B400D6 for ; Wed, 25 May 2022 10:19:01 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 6BD695C00E2; Wed, 25 May 2022 04:19:01 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 25 May 2022 04:19:01 -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=fm1; t=1653466741; x= 1653553141; bh=0w/Lb1VLKQJdqh6QXpPbWAqwaW1y3Ex51yK5JC0EV1g=; b=H pIcfBYUJ2CZAzNgTx9gp8DYeQ3jL3HNWvCX1ZZtfCFuZYULHgR65bqV4eO/LOBfM 0k64lgo5bsV48y8wr5kB+uo66KNRaMMSsnifq8Fo+9DBGJOu8JYIcx8RlQuuyL5G UMHYe0STxl9aQW+HaZhKPVf/7W56svLo7WbS+1Swgkv+9LJTWUSCi14NfrOWtpqy A/bPFtMUHlY0n0Fq4s/f6B+8Pj8HgJ/foZ48Kxcqb5rMCTWKhivbtJ9BbcM/kPti NwRogKO7qiveNWyBE3n6fTW66sN4J5EDjxvg8RmYHq5QXpfzfx5Pva+565fnYOYq aviZ+whbuHj2nUv+m5Wqw== 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=fm1; t=1653466741; x= 1653553141; bh=0w/Lb1VLKQJdqh6QXpPbWAqwaW1y3Ex51yK5JC0EV1g=; b=t Esyhe/RpyMQIrNoJg6kuBU8s+A9zI4sd23OWsaXRWzyw3dJnkPXKRIP3qohMlWiP BglHHfgPITp6DdYaeA3iXfrwwegwwKRtJRryUCaS2NXUEl+Ke28+aM5444Ph5Bo8 B/tRjV//rcSjMXNEcwps9jV7xa78WE78s2ylGGb3N5QsqbXM2BhcaTE1KPS+b6UJ YxM7XUtX1+sPn4hUaB9XZJjYMnmfdd1LNbskolWmkCIl11dl7B/iQn0rDmvleZaa ZjhYe+Mp/Ge/LiE1/BeGv7FEDc8LcxNpDuA0Rh6NVficSe1bMeUUbhzydR47Dd29 5BpTK/nQI0H7kWjN5H86A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrjeehgddtvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddtieek gfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 25 May 2022 04:18:58 -0400 (EDT) From: Thomas Monjalon To: Bruce Richardson , David Christensen Cc: dev@dpdk.org, Beilei Xing , Matan Azrad , Viacheslav Ovsiienko , Maxime Coquelin , Chenbo Xia , Vladimir Medvedkin Subject: Re: [PATCH] avoid AltiVec keyword vector Date: Wed, 25 May 2022 10:18:51 +0200 Message-ID: <10083511.U7f9L36N0a@thomas> In-Reply-To: References: <20220503120321.2438479-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 04/05/2022 22:40, David Christensen: > On 5/3/22 5:03 AM, Thomas Monjalon wrote: > > The keyword "vector" may conflict easily. > > As a rule, it is better to use the alternative keyword "__vector". > > > > Signed-off-by: Thomas Monjalon > > Reviewed-by: David Christensen Applied with a longer explanation: The AltiVec header file is defining "vector", except in C++ build. The keyword "vector" may conflict easily. As a rule, it is better to use the alternative keyword "__vector", so we will be able to #undef vector after including AltiVec header. Later it may become possible to #undef vector in rte_altivec.h with a compatibility breakage.