DPDK patches and discussions
 help / color / mirror / Atom feed
From: Adham Masarwah <adham@mellanox.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "Menon, Ranjit" <ranjit.menon@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Omar Cardona <ocardona@microsoft.com>,
	Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>,
	Jeffrey Tippet <Jeffrey.Tippet@microsoft.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, 21 May 2019 14:33:36 +0000	[thread overview]
Message-ID: <VI1PR05MB58211ACB353C22BFEC63FBFBC4070@VI1PR05MB5821.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20190521135236.GA1364@bricha3-MOBL.ger.corp.intel.com>

On Tue, May 21, 2019 at 01:41:06PM +0000, Adham Masarwah wrote:
> > 
> > >From: Bruce Richardson <bruce.richardson@intel.com>
> > >Sent: Tuesday, May 21, 2019 11:22 AM
> > >
> > >On Mon, May 20, 2019 at 07:02:22PM +0100, Menon, Ranjit wrote:
> > >>    Adham…
> > >> 
> > >>    I don’t think we debugged using clang compiled code for Hello world –
> > >>    mainly because it was only a “helloworld” application and we didn’t
> > >>    quite need any debugging!:-)
> > >> 
> > >> 
> > >>    I found this link:
> > >>    [1]https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.llvm.org%2F2017%2F08%2Fllvm-on-windows-now-supports-pdb-debug&amp;data=02%7C01%7Cadham%40mellanox.com%7Cd44c2914a2104176185008d6ddf39932%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636940435668687736&amp;sdata=%2BXND%2Be8KTPd6CBligMrSlJzsV%2BrrxnHKjQvcClwpNDk%3D&amp;reserved=0.
> > >>    html
> > >> 
> > >>    …which says to use the following:
> > >> 
> > >>     Here are two simple ways to test out this new functionality:
> > >>     1. Have clang-cl invoke lld automatically
> > >> 
> > >>         clang-cl -fuse-ld=lld -Z7 -MTd hello.cpp
> > >>     2. Invoke clang-cl and lld separately.
> > >> 
> > >>    clang-cl -c -Z7 -MTd -o hello.obj hello.cpp
> > >> 
> > >>    lld-link -debug hello.obj
> > >> 
> > >>    Can you try it with just the -Z7 option?
> > >> 
> > >> 
> > >>    I’m also adding some persons from Microsoft to this thread, hoping they
> > >>    can help…
> > >> 
> > >> 
> > >>    +Harini +Omar +Jeffrey
> > >> 
> > >> 
> > >>    ranjit m.
> > >> 
> > >Part of the issue may be that we use clang, rather than clang-cl on windows.
> > >
> > >/Bruce
> > 
> > I did a small test to check clang vs clang-cl, the compiled binary and the PDB file from the Clang-cl seems working fine in WinDbg.
> > The problem we have that the meson.build files are not compatible with clang-cl, and the meson build command is failing.
> > This is the first error:
> > config\x86\meson.build:23:1: ERROR: Problem encountered: SSE4.2 instruction set is required for DPDK.
> > Please set the machine type to "nehalem" or "corei7" or higher value
> > 
> > /Adham
> 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.
> 
> /Bruce
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 ? 

  reply	other threads:[~2019-05-21 14:33 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 [this message]
2019-06-04  8:43           ` 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=VI1PR05MB58211ACB353C22BFEC63FBFBC4070@VI1PR05MB5821.eurprd05.prod.outlook.com \
    --to=adham@mellanox.com \
    --cc=Harini.Ramakrishnan@microsoft.com \
    --cc=Jeffrey.Tippet@microsoft.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).