From: Thomas Monjalon <thomas@monjalon.net>
To: Jason Messer <jmesser@microsoft.com>,
Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>,
Omar Cardona <ocardona@microsoft.com>,
Ranjit Menon <ranjit.menon@intel.com>
Cc: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Jeff Shaw" <jeffrey.b.shaw@intel.com>,
stephen@networkplumber.org, dev@dpdk.org
Subject: [dpdk-dev] Compiler for Windows
Date: Wed, 02 Jan 2019 23:45:22 +0100 [thread overview]
Message-ID: <7824863.MkUOD0j12R@xps> (raw)
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
next reply other threads:[~2019-01-02 22:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 22:45 Thomas Monjalon [this message]
2019-01-03 6:33 ` Stephen Hemminger
2019-01-03 17:10 ` Jason Messer
2019-01-03 17:32 ` Thomas Monjalon
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=7824863.MkUOD0j12R@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=harini.ramakrishnan@microsoft.com \
--cc=jeffrey.b.shaw@intel.com \
--cc=jmesser@microsoft.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).