From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id 81B16568A for ; Fri, 8 Jul 2016 10:05:46 +0200 (CEST) Received: by mail-wm0-f46.google.com with SMTP id n127so7660813wme.1 for ; Fri, 08 Jul 2016 01:05:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=aABvr8tjadhp9iXt9At2ijSi5Um4gBBn7Rn9TXDiRa8=; b=xuCLjPChLIx84b1ezj1ozaZhwLEY8UG9VATYsOUNDUzOGU6WkyrGmnsJY9FR1+PWJB q/vN/E3cHm/dDHGs2eLrcvZXxEHPBz2piCNVGNut9+x6dnieB9eHIAvI7wC66Zp0T3L1 Bn0N9yrYTkWxxHWXR0X+GEgUniIh6Fp2Tu+xj75IRFYbTITWGxx+IYWCO4Exdi7uJxjx 0IP1BGQ4cYrzlje04Z4uBxVBeAw/ogxfBL4WkNhk0MJj/r50Uw0k2REFUa90Y4g3DL3Y gp7Hmzd6PSWQfaLIDy2zv5ivRNmiz24folFaCn6k22SUiCzdBw2cm51iGjPwuvZ2Bd3i iefg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=aABvr8tjadhp9iXt9At2ijSi5Um4gBBn7Rn9TXDiRa8=; b=jXbPotkTGlNN1UMXNzP653d5xVDuoh6DygicXO+Q59N21LFRoAYcxGCTY3jNb8xXss DTuq6DlLqte2KcDPt0iu1/avpCiRu/LsAYBwgiLdfyoJgFFsStXy4x45HTFaRuRAbSfa 4AoXpHtGTuRCyDNcUdHFRIaLOH7YnBOUkUbwz06lfvX6UOaAXdZAAvZpaEO2Dd1bJPxo WBqMUUl9sIydIAZcMEMN/BVd3JyCNY3wq2wL9waJb79oJRRfCYdMM9a2SVqpweqYKhyD QwSIx+HOWgOAEq5JZ/Uvfd532/Gg4SRBUdnIn5XBFie0oXRfPAEDTJiHpbGdW4WUfEHj Qf4Q== X-Gm-Message-State: ALyK8tJn511yrTgzZ1zfDA5a8/q1EjUvPTkuV5ure3MK9OK8xYLLiFgqUh3Jbw7nfo9gYwRX X-Received: by 10.28.181.146 with SMTP id e140mr1981342wmf.38.1467965146327; Fri, 08 Jul 2016 01:05:46 -0700 (PDT) Received: from 6wind.com (guy78-3-82-239-227-177.fbx.proxad.net. [82.239.227.177]) by smtp.gmail.com with ESMTPSA id o10sm1787528wjs.38.2016.07.08.01.05.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Jul 2016 01:05:45 -0700 (PDT) Date: Fri, 8 Jul 2016 10:05:43 +0200 From: Adrien Mazarguil To: "Wiles, Keith" Cc: "dev@dpdk.org" Message-ID: <20160708080543.GB7621@6wind.com> Mail-Followup-To: "Wiles, Keith" , "dev@dpdk.org" References: <10B01822-557C-400A-A6BE-DBFF60AF90E4@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10B01822-557C-400A-A6BE-DBFF60AF90E4@intel.com> Subject: Re: [dpdk-dev] [PATCH v3 00/11] Fix build errors related to exported headers X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 08:05:46 -0000 On Thu, Jul 07, 2016 at 06:33:17PM +0000, Wiles, Keith wrote: > > > On Jul 7, 2016, at 10:49 AM, Adrien Mazarguil wrote: > > > > DPDK uses GNU C language extensions in most of its code base. This is fine > > for internal source files whose compilation flags are controlled by DPDK, > > however user applications that use exported "public" headers may experience > > compilation failures when enabling strict error/standard checks (-std and > > -pedantic for instance). > > Do you try compiling these changes with CLANG and/or ICC compilers? clang/clang++ yes, works fine. I did not try with ICC however. Note that considering "({ ... })" is a GNU extension, compilers that do support this syntax also support the GNU __extension__ keyword. As a result, those that do not support this keyword most likely already cannot compile DPDK at all. -- Adrien Mazarguil 6WIND