From: Stephen Hemminger <stephen@networkplumber.org>
To: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: mlx5: unitialized warning
Date: Fri, 17 Dec 2021 12:17:21 -0800 [thread overview]
Message-ID: <20211217121721.5b34b62c@hermes.local> (raw)
In-Reply-To: <MN2PR12MB308791A0CBF1967AC469BAFEB9789@MN2PR12MB3087.namprd12.prod.outlook.com>
On Fri, 17 Dec 2021 19:28:26 +0000
Dmitry Kozlyuk <dkozlyuk@nvidia.com> wrote:
> > > I don't see this warning with gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04).
> [...]
> >
> > It maybe because I was testing with thread santizer enabled and compiler
> > was doing different optimizations.
>
> Reproduced with -Dc_args=-fsanitize=thread, thanks!
I was using
-Db_sanitize=thread
which is the meson way to do it
prev parent reply other threads:[~2021-12-17 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 18:05 Stephen Hemminger
2021-12-17 19:01 ` Dmitry Kozlyuk
2021-12-17 19:19 ` Stephen Hemminger
2021-12-17 19:28 ` Dmitry Kozlyuk
2021-12-17 20:17 ` Stephen Hemminger [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=20211217121721.5b34b62c@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=dkozlyuk@nvidia.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).