DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jason Messer <jmesser@microsoft.com>
Cc: "Stephen Hemminger" <stephen@networkplumber.org>,
	"Harini Ramakrishnan" <Harini.Ramakrishnan@microsoft.com>,
	"Omar Cardona" <ocardona@microsoft.com>,
	"'Ranjit Menon'" <ranjit.menon@intel.com>,
	"'Mattias Rönnblom'" <mattias.ronnblom@ericsson.com>,
	"'Jeff Shaw'" <jeffrey.b.shaw@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Jeffrey Tippet" <Jeffrey.Tippet@microsoft.com>,
	"Deval, Manasi" <manasi.deval@intel.com>
Subject: Re: [dpdk-dev] Compiler for Windows
Date: Thu, 03 Jan 2019 18:32:45 +0100	[thread overview]
Message-ID: <10666701.GC44MuPZhG@xps> (raw)
In-Reply-To: <SN4PR2101MB0877FD5D0E1B5081A98A366BB48D0@SN4PR2101MB0877.namprd21.prod.outlook.com>

Hi Jason,

We need to get facts in order to do a good decision.
Please, let's give detailed feedback for each option.

03/01/2019 18:10, Jason Messer:
> +Jeffrey, Manasi
> 
> We will get the most traction from the Windows developer community
> if we use msvc. The only thing preventing that last time was
> GNU extensions used in DPDK source which were not ISO C standards
> compliant.

I think the main issue is that MSVC is not C99 compliant.

> We were also experimenting with Clang/LLVM running natively on Windows
> host but ran into a bunch of issues (maybe others made further progress?).

Chromium is built with clang on Windows, so I wonder what prevents us
to use it?

> GCC using Windows Subsystem for Linux (WSL) would be an interesting
> option and could be a secondary option for MSVC for Windows developers.

I thought GCC on WSL would build a Linux binary?
Can we build a Windows native binary with it?

What about mingw-w64? Is there any drawback?


> From: Stephen Hemminger <stephen@networkplumber.org> 
> > What about Gcc under the WSL thing (ie Linux emulation in Windows).
> > Much better than Cygwin type stuff.
> > 
> > From: Thomas Monjalon <thomas@monjalon.net>
> > > Hi,
> > > 
> > > We need to gather inputs about the pros/cons of the C compilers
> > > available for Windows.
> > > 
> > > Interesting criterias could be:
> > > 	- ease of use
> > > 	- availability
> > > 	- standards compliance
> > > 	- performance
> > > 
> > > When the comparison will be complete, we should publish it in the doc/
> > > directory, while porting DPDK to Windows.
> > > 
> > > I start with few data:
> > > 
> > > * gcc|clang on cygwin
> > > 
> > > 	- not native
> > > 
> > > * gcc/mingw
> > > 
> > > * gcc/mingw-w64
> > > 
> > > * clang/mingw-w64
> > > 
> > > * clang --target=x86_64-windows-msvc
> > > 
> > > * icc
> > > 
> > > 	- not freely available
> > > 
> > > * msvc
> > > 
> > > 	- native
> > > 	- specific command line
> > > 	- not C99

  reply	other threads:[~2019-01-03 17:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 22:45 Thomas Monjalon
2019-01-03  6:33 ` Stephen Hemminger
2019-01-03 17:10   ` Jason Messer
2019-01-03 17:32     ` Thomas Monjalon [this message]
2019-01-03 22:46     ` Wiles, Keith
2019-01-07 10:56   ` Burakov, Anatoly
2019-01-07 15:51     ` Stephen Hemminger
2019-01-07 16:15       ` Bruce Richardson
2019-01-07 16:29         ` Burakov, Anatoly
2019-01-07 16:51           ` Stephen Hemminger
2019-01-07 17:00             ` Bruce Richardson
2019-01-07 17:08               ` Thomas Monjalon
2019-01-08 10:24                 ` Burakov, Anatoly
2019-01-30 14:21                   ` Thomas Monjalon
2019-01-30 16:32                     ` Menon, Ranjit
2019-01-31 17:12                       ` Wiles, Keith
2019-01-31 17:36                         ` Thomas Monjalon
2019-01-31 17:48                           ` Wiles, Keith
2019-02-13 16:11                       ` Thomas Monjalon
2019-02-13 16:35                         ` Menon, Ranjit
2019-01-08 12:51               ` Morten Brørup
2019-01-08 14:10                 ` Mattias Rönnblom
2019-01-07 17:00             ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=10666701.GC44MuPZhG@xps \
    --to=thomas@monjalon.net \
    --cc=Harini.Ramakrishnan@microsoft.com \
    --cc=Jeffrey.Tippet@microsoft.com \
    --cc=dev@dpdk.org \
    --cc=jeffrey.b.shaw@intel.com \
    --cc=jmesser@microsoft.com \
    --cc=manasi.deval@intel.com \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=ocardona@microsoft.com \
    --cc=ranjit.menon@intel.com \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).