From: Thomas Monjalon <thomas@monjalon.net>
To: Omar Cardona <ocardona@microsoft.com>,
Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>,
Jeffrey Tippet <Jeffrey.Tippet@microsoft.com>
Cc: dev@dpdk.org, Adham Masarwah <adham@mellanox.com>,
Bruce Richardson <bruce.richardson@intel.com>,
"Menon, Ranjit" <ranjit.menon@intel.com>,
"Kadam, Pallavi" <pallavi.kadam@intel.com>,
Yohad Tor <yohadt@mellanox.com>,
Rani Sharoni <ranish@mellanox.com>,
Tal Shnaiderman <talshn@mellanox.com>
Subject: Re: [dpdk-dev] Generating Debug information in Windows using Clang (PDB files)
Date: Tue, 04 Jun 2019 10:43:59 +0200 [thread overview]
Message-ID: <2002358.ryAd6E37yW@xps> (raw)
In-Reply-To: <VI1PR05MB58211ACB353C22BFEC63FBFBC4070@VI1PR05MB5821.eurprd05.prod.outlook.com>
21/05/2019 16:33, Adham Masarwah:
> From: Bruce Richardson <bruce.richardson@intel.com>
> > Yes, the clang-cl compiler (like msvc) does not offer the flags we need to control the exact output microarchitecture. It also uses completely different flag formats for things like warnings etc, which is why we need to use clang instead.
>
> In this case we should find a solution to open the debug ability since we will need it for sure.
> What can be done, who can help causing clang generates good files ?
Please, some help from Microsoft would be very appreciated.
Thanks
prev parent reply other threads:[~2019-06-04 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 10:27 Adham Masarwah
2019-05-20 18:02 ` Menon, Ranjit
2019-05-21 8:22 ` Bruce Richardson
2019-05-21 13:41 ` Adham Masarwah
2019-05-21 13:52 ` Bruce Richardson
2019-05-21 14:33 ` Adham Masarwah
2019-06-04 8:43 ` Thomas Monjalon [this message]
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=2002358.ryAd6E37yW@xps \
--to=thomas@monjalon.net \
--cc=Harini.Ramakrishnan@microsoft.com \
--cc=Jeffrey.Tippet@microsoft.com \
--cc=adham@mellanox.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranish@mellanox.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@mellanox.com \
--cc=yohadt@mellanox.com \
/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).