DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [RFC 0/8] Gcc-12 warning fixes
Date: Tue,  7 Jun 2022 10:17:38 -0700	[thread overview]
Message-ID: <20220607171746.461772-1-stephen@networkplumber.org> (raw)

Ths is early proposal on how to address some of the gcc-12
warnings. Most of these are related to rte_memcpy which can
simply be addressed by using regular memcpy instead.

Stephen Hemminger (8):
  net/ena: fix warnings related to rte_memcpy and gcc-12
  net/qede: fix gcc-12 rte_memcpy warnings
  net/ice: fix rte_memcpy warnings with gcc-12
  test/ipfrag: fix gcc-12 warnings
  test/ipsec: fix gcc-12 rte_memcpy warnings
  net/enetfc: fix array out of bounds warning
  vhost: replace rte_memcpy to fix warning
  ip_frag: fix gcc-12 warnings

 app/test/test_ipfrag.c               | 13 ++++++-----
 app/test/test_ipsec.c                | 13 ++++++-----
 drivers/net/ena/base/ena_plat_dpdk.h | 10 +--------
 drivers/net/ena/ena_ethdev.c         |  8 +++----
 drivers/net/ena/ena_rss.c            |  2 +-
 drivers/net/enetfec/enet_ethdev.c    |  5 +++++
 drivers/net/ice/base/ice_osdep.h     |  5 ++---
 drivers/net/ice/ice_dcf.c            | 12 +++++------
 drivers/net/ice/ice_dcf_ethdev.c     | 10 ++++-----
 drivers/net/ice/ice_dcf_parent.c     |  2 +-
 drivers/net/ice/ice_dcf_sched.c      | 11 +++++-----
 drivers/net/ice/ice_ethdev.c         | 13 ++++++-----
 drivers/net/ice/ice_fdir_filter.c    | 32 ++++++++++++++--------------
 drivers/net/ice/ice_tm.c             |  6 +++---
 drivers/net/qede/base/bcm_osal.h     |  3 +--
 drivers/net/qede/qede_ethdev.c       |  2 +-
 drivers/net/qede/qede_filter.c       | 16 ++++++--------
 drivers/net/qede/qede_main.c         | 13 ++++++-----
 drivers/net/qede/qede_sriov.c        |  6 +++---
 lib/ip_frag/rte_ipv4_fragmentation.c |  7 +++---
 lib/vhost/vhost_crypto.c             |  2 +-
 21 files changed, 88 insertions(+), 103 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-06-07 17:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 17:17 Stephen Hemminger [this message]
2022-06-07 17:17 ` [RFC 1/8] net/ena: fix warnings related to rte_memcpy and gcc-12 Stephen Hemminger
2022-06-08 12:29   ` Michał Krawczyk
2022-06-08 15:32     ` Stephen Hemminger
2022-06-08 19:18       ` Michał Krawczyk
2022-06-08 20:52         ` Stephen Hemminger
2022-06-07 17:17 ` [RFC 2/8] net/qede: fix gcc-12 rte_memcpy warnings Stephen Hemminger
2022-06-23 14:16   ` David Marchand
2022-06-07 17:17 ` [RFC 3/8] net/ice: fix rte_memcpy warnings with gcc-12 Stephen Hemminger
2022-06-07 17:17 ` [RFC 4/8] test/ipfrag: fix gcc-12 warnings Stephen Hemminger
2022-06-07 17:17 ` [RFC 5/8] test/ipsec: fix gcc-12 rte_memcpy warnings Stephen Hemminger
2022-06-07 17:17 ` [RFC 6/8] net/enetfc: fix array out of bounds warning Stephen Hemminger
2022-06-07 17:17 ` [RFC 7/8] vhost: replace rte_memcpy to fix warning Stephen Hemminger
2022-06-07 17:17 ` [RFC 8/8] ip_frag: fix gcc-12 warnings Stephen Hemminger
2022-06-08  8:19   ` Konstantin Ananyev
2022-06-08 15:26     ` Stephen Hemminger
2022-06-09  7:09       ` Morten Brørup
2022-06-14 21:20         ` 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=20220607171746.461772-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --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).