From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Montorsi, Francesco" Subject: Re: warnings when including DPDK headers from a C++17 source file Date: Sun, 15 Jul 2018 13:00:16 +0000 Message-ID: <1531659613771.95891@empirix.com> References: <1531489881821.76380@empirix.com>, <20180713085205.1a255bf3@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" To: Stephen Hemminger Return-path: Received: from bilemail1.empirix.com (bilemail1.empirix.com [208.67.76.245]) by dpdk.org (Postfix) with ESMTP id 397052BD8 for ; Sun, 15 Jul 2018 15:00:18 +0200 (CEST) In-Reply-To: <20180713085205.1a255bf3@xeon-e3> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi,=0A= =0A= ________________________________________=0A= From: Stephen Hemminger =0A= Sent: Friday, July 13, 2018 5:52 PM=0A= To: Montorsi, Francesco=0A= Cc: dev@dpdk.org=0A= Subject: Re: [dpdk-dev] warnings when including DPDK headers from a C++17 s= ource file=0A= =0A= > Why is DPDK code using register keyword at all? It is ignored by modern c= ompilers.=0A= =0A= that's my question as well :)=0A= =0A= Maybe register keyword could be removed at least from header files to make = the life easier to whoever is using C++17... right now I worked around that= by placing -Werror -Wno-register, but that's perhaps not the best solution= =0A= =0A= Francesco=0A= =0A=