DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 0/2] remove compiler warnings with icc using meson
Date: Fri, 24 Jan 2020 15:37:53 +0000	[thread overview]
Message-ID: <20200124153755.13939-1-bruce.richardson@intel.com> (raw)

While icc can compile DPDK successfully using a meson/ninja build, there
are a lot of warnings issued in the process, which means that any use of
werror flag will break the build, and the output just looks messy and
possibly worrying to the user.

To improve this situation, we can fix the warnings about unsupported
compiler flags, and just maintain a list of icc warnings to ignore.

Bruce Richardson (2):
  net/octeontx2: check compiler flag before use
  build: remove warnings for builds with icc

 config/meson.build                | 6 ++++++
 drivers/net/octeontx2/meson.build | 4 +---
 2 files changed, 7 insertions(+), 3 deletions(-)

-- 
2.20.1


             reply	other threads:[~2020-01-24 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 15:37 Bruce Richardson [this message]
2020-01-24 15:37 ` [dpdk-dev] [PATCH 1/2] net/octeontx2: check compiler flag before use Bruce Richardson
2020-01-28 16:55   ` Jerin Jacob
2020-01-24 15:37 ` [dpdk-dev] [PATCH 2/2] build: remove warnings for builds with icc Bruce Richardson
2020-01-24 15:51   ` Burakov, Anatoly
2020-01-24 16:34     ` Bruce Richardson
2020-02-06  2:23 ` [dpdk-dev] [PATCH 0/2] remove compiler warnings with icc using meson 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=20200124153755.13939-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.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).