From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 0CE731B273 for ; Mon, 7 Jan 2019 18:08:33 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6695621947; Mon, 7 Jan 2019 12:08:32 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 07 Jan 2019 12:08:32 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=P7ggmmhxl3pATUOW+I+3qqvbN+9fbyRVEaw8HjYHnnE=; b=jTzospcvcj9G wtBg5Vy9/UNVZBEZYU2kiVkWe0MdTbdUlPZW3CjARVnhgsuA4LStM617k0QIouNF sXvHUCNHc+4aJzAYPt8aARAowzW9UBLBu5x5Hth4ODkxieocg6eqk7NVAXd25Pj8 3hmKVCZAg0AuSR5QbKb7n3eMLSONidk= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=P7ggmmhxl3pATUOW+I+3qqvbN+9fbyRVEaw8HjYHn nE=; b=egMZYF70ioRdht678P7dHH2ZrBSeU7KaN2t1GIuAZY5mqx6rH2YMaXRF5 tizwBRHM3RobNIPc4UOEiTlQhGbj2lGVwHcJsLNjWUASYd77fNN1lAnq/eUgUp/J DEqhmfOIjYAWdIF4XXi6bys7My/d90/lOjTq45mqQfLb5v8H1Di4QTNEaiQ2TYNI 06y3MiD6EPmBnueNwumgY5n+hU7au59mBbAxHP4Pdf1EPAbOTFenGHWGOjr6X+BS zqGxnhKmazwNepKtd0U6KUAlkhbbjH8nxL/btkuS+RruxCjRtHFhKUCzEV6qklHP DENBcrbZJEP8UrziQe455om7AxTxw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrvdejgdelheculddtuddrgedtkedrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 3E152100BA; Mon, 7 Jan 2019 12:08:30 -0500 (EST) From: Thomas Monjalon To: Bruce Richardson Cc: Stephen Hemminger , "Burakov, Anatoly" , 'Jason Messer' , 'Harini Ramakrishnan' , 'Omar Cardona' , 'Ranjit Menon' , 'Mattias =?ISO-8859-1?Q?R=F6nnblom=27?= , 'Jeff Shaw' , dev@dpdk.org Date: Mon, 07 Jan 2019 18:08:28 +0100 Message-ID: <24170945.hIekyy4cRm@xps> In-Reply-To: <20190107170021.GB23828@bricha3-MOBL.ger.corp.intel.com> References: <7824863.MkUOD0j12R@xps> <20190107085125.3e3adf05@hermes.lan> <20190107170021.GB23828@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Compiler for Windows X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2019 17:08:33 -0000 07/01/2019 18:00, Bruce Richardson: > I think for windows we probably want to start with the MS compiler first, > since from my understanding it's probably the default go-to compiler for > developers on windows, and look at alternatives from there. Not sure. I feel clang is a better option. This is the purpose of this thread: which compiler can work with the DPDK code base? Which modifications of code are acceptable? Unfortunately we lost my original attempt of getting some facts.