DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/5] fix build with option -O1
Date: Fri, 16 Nov 2018 17:58:49 +0100	[thread overview]
Message-ID: <20181116165854.24017-1-thomas@monjalon.net> (raw)

When trying to compile with -O1, the compiler
shows some errors. Some are justified, others look like
compiler bug. Anyway, it's better to fix all of them.


Thomas Monjalon (5):
  eal: fix build with -O1
  kni: fix possible uninitialized variable
  net/mlx4: fix possible uninitialized variable
  eventdev: fix possible uninitialized variable
  app/eventdev: fix possible uninitialized variable

 app/test-eventdev/test_pipeline_common.c       | 2 +-
 drivers/net/mlx4/mlx4_ethdev.c                 | 2 ++
 lib/librte_eal/common/include/rte_common.h     | 9 ---------
 lib/librte_eventdev/rte_event_eth_tx_adapter.c | 2 +-
 lib/librte_kni/rte_kni.c                       | 2 +-
 5 files changed, 5 insertions(+), 12 deletions(-)

-- 
2.19.0

             reply	other threads:[~2018-11-16 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 16:58 Thomas Monjalon [this message]
2018-11-16 16:58 ` [dpdk-dev] [PATCH 1/5] eal: fix build with -O1 Thomas Monjalon
2018-11-16 16:58 ` [dpdk-dev] [PATCH 2/5] kni: fix possible uninitialized variable Thomas Monjalon
2018-11-16 16:58 ` [dpdk-dev] [PATCH 3/5] net/mlx4: " Thomas Monjalon
2018-11-16 16:58 ` [dpdk-dev] [PATCH 4/5] eventdev: " Thomas Monjalon
2018-11-16 16:58 ` [dpdk-dev] [PATCH 5/5] app/eventdev: " Thomas Monjalon
2018-11-23  0:26 ` [dpdk-dev] [PATCH 0/5] fix build with option -O1 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=20181116165854.24017-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --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).