DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: <dev@dpdk.org>, <stephen@networkplumber.org>
Subject: Re: [PATCH v13 0/3] add diagnostics macros to make code portable
Date: Thu, 16 Jan 2025 08:58:05 +0000	[thread overview]
Message-ID: <Z4jKHaI4hMFCRFUN@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <1736992511-20462-1-git-send-email-andremue@linux.microsoft.com>

On Wed, Jan 15, 2025 at 05:55:08PM -0800, Andre Muezerie wrote:
> It was a common pattern to have "GCC diagnostic ignored" pragmas
> sprinkled over the code and only activate these pragmas for certain
> compilers (gcc and clang). Clang supports GCC's pragma for
> compatibility with existing source code, so #pragma GCC diagnostic
> and #pragma clang diagnostic are synonyms for Clang
> (https://clang.llvm.org/docs/UsersManual.html).
> 
> Now that effort is being made to make the code compatible with MSVC
> these expressions would become more complex. It makes sense to hide
> this complexity behind macros. This makes maintenance easier as these
> macros are defined in a single place. As a plus the code becomes
> more readable as well.
> 

Series-acked-by: Bruce Richardson <bruce.richardson@intel.com>

> v13:
>  * Renamed RTE_IGNORE_CAST_QUAL into RTE_PTR_DROP_QUALIFIERS.
>  * Added (void *) cast to RTE_PTR_DROP_QUALIFIERS to avoid the need
>    for casting the result in most places where the macro is used.
> 
> v12:
>  * Added macro RTE_IGNORE_CAST_QUAL and used it as a more compact and
>    readable form to suppress warnings where a cast is used to remove
>    a type qualifier.
> 
> v11:
>  * Added __rte_diagnostic_ignored_wcast_qual to a few more places where
>    it was needed.
> 
> v10:
>  * Added __rte_diagnostic_ignored_wcast_qual to a few more places where
>    it was needed.
> 
> v9:
>  * Added __rte_diagnostic_ignored_wcast_qual to a few more places where
>    it was needed.
> 
> v8:
>  * Added __rte_diagnostic_ignored_wcast_qual to a few more places where
>    it was needed.
> 
> v7:
>  * Added __rte_diagnostic_ignored_wcast_qual to a few more places where
>    it was needed.
> 
> v6:
>  * Added __rte_diagnostic_ignored_wcast_qual to a few more places where
>    it was needed.
> 
> v5:
>  * Added __rte_diagnostic_ignored_wcast_qual to a few more places where
>    it was needed.
> 
> v4:
>  * Added __rte_diagnostic_ignored_wcast_qual to a few more places where
>    it was needed.
> 
> v3:
>  * Added __rte_diagnostic_ignored_wcast_qual to a few more places where
>    it was needed.
> 
> v2:
>  * Removed __rte_diagnostic_ignored_wstrict_aliasing (introduced
>    in v1).
>  * Removed the pragmas from many files where they were not needed.
>  * In the files where the pragmas were indeed needed, reduced the
>    scope during which they are active, reducing the chance that
>    unforeseen issues are hidden due to warning suppression.
> 
> Andre Muezerie (3):
>   eal: add diagnostics macros to make code portable
>   drivers/common: add diagnostics macros to make code portable
>   drivers/net: add diagnostics macros to make code portable
> 
>  drivers/common/idpf/idpf_common_rxtx_avx512.c | 77 ++++++++---------
>  drivers/net/axgbe/axgbe_rxtx.h                |  9 --
>  drivers/net/cpfl/cpfl_rxtx_vec_common.h       |  4 -
>  drivers/net/dpaa2/dpaa2_rxtx.c                | 15 +---
>  drivers/net/fm10k/fm10k_rxtx_vec.c            | 20 ++---
>  drivers/net/hns3/hns3_rxtx_vec_neon.h         |  6 +-
>  .../net/i40e/i40e_recycle_mbufs_vec_common.c  |  2 -
>  drivers/net/i40e/i40e_rxtx_common_avx.h       | 24 +++---
>  drivers/net/i40e/i40e_rxtx_vec_altivec.c      | 23 ++---
>  drivers/net/i40e/i40e_rxtx_vec_avx2.c         | 40 +++++----
>  drivers/net/i40e/i40e_rxtx_vec_avx512.c       | 30 ++++---
>  drivers/net/i40e/i40e_rxtx_vec_common.h       |  4 -
>  drivers/net/i40e/i40e_rxtx_vec_neon.c         | 39 ++++-----
>  drivers/net/i40e/i40e_rxtx_vec_sse.c          | 32 +++----
>  drivers/net/iavf/iavf_rxtx_vec_avx2.c         | 84 ++++++++++---------
>  drivers/net/iavf/iavf_rxtx_vec_avx512.c       | 78 ++++++++---------
>  drivers/net/iavf/iavf_rxtx_vec_common.h       | 12 ++-
>  drivers/net/iavf/iavf_rxtx_vec_neon.c         | 26 +++---
>  drivers/net/iavf/iavf_rxtx_vec_sse.c          | 52 ++++++------
>  drivers/net/ice/ice_rxtx_common_avx.h         | 24 +++---
>  drivers/net/ice/ice_rxtx_vec_avx2.c           | 74 ++++++++--------
>  drivers/net/ice/ice_rxtx_vec_avx512.c         | 64 ++++++--------
>  drivers/net/ice/ice_rxtx_vec_common.h         |  4 -
>  drivers/net/ice/ice_rxtx_vec_sse.c            | 28 +++----
>  drivers/net/idpf/idpf_rxtx_vec_common.h       |  4 -
>  .../ixgbe/ixgbe_recycle_mbufs_vec_common.c    |  2 -
>  drivers/net/ixgbe/ixgbe_rxtx_vec_neon.c       | 18 ++--
>  drivers/net/ixgbe/ixgbe_rxtx_vec_sse.c        | 20 ++---
>  drivers/net/mlx5/mlx5_flow.c                  |  5 +-
>  drivers/net/mlx5/mlx5_rxtx_vec_altivec.h      |  5 --
>  drivers/net/mlx5/mlx5_rxtx_vec_neon.h         | 18 ++--
>  drivers/net/mlx5/mlx5_rxtx_vec_sse.h          | 71 +++++++++-------
>  drivers/net/ngbe/ngbe_rxtx_vec_neon.c         |  8 +-
>  drivers/net/tap/tap_flow.c                    |  6 +-
>  drivers/net/txgbe/txgbe_rxtx_vec_neon.c       |  8 +-
>  drivers/net/virtio/virtio_rxtx_simple.c       |  4 -
>  lib/eal/include/rte_common.h                  | 29 +++++++
>  37 files changed, 466 insertions(+), 503 deletions(-)
> 
> --
> 2.47.2.vfs.0.0
> 

      parent reply	other threads:[~2025-01-16  8:58 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27  1:33 [PATCH " Andre Muezerie
2024-12-27  1:33 ` [PATCH 1/3] lib/eal: " Andre Muezerie
2024-12-27  1:33 ` [PATCH 2/3] drivers/common: " Andre Muezerie
2024-12-27 17:57   ` Stephen Hemminger
2024-12-27 19:43     ` Andre Muezerie
2024-12-27  1:33 ` [PATCH 3/3] drivers/net: " Andre Muezerie
2024-12-28  0:45 ` [PATCH v2 0/3] " Andre Muezerie
2024-12-28  0:45   ` [PATCH v2 1/3] lib/eal: " Andre Muezerie
2024-12-28  0:45   ` [PATCH v2 2/3] drivers/common: " Andre Muezerie
2024-12-28  0:45   ` [PATCH v2 3/3] drivers/net: " Andre Muezerie
2024-12-28  3:18 ` [PATCH v3 0/3] " Andre Muezerie
2024-12-28  3:18   ` [PATCH v3 1/3] lib/eal: " Andre Muezerie
2024-12-28  3:18   ` [PATCH v3 2/3] drivers/common: " Andre Muezerie
2024-12-28  3:18   ` [PATCH v3 3/3] drivers/net: " Andre Muezerie
2024-12-30 15:59 ` [PATCH v4 0/3] " Andre Muezerie
2024-12-30 15:59   ` [PATCH v4 1/3] lib/eal: " Andre Muezerie
2024-12-30 15:59   ` [PATCH v4 2/3] drivers/common: " Andre Muezerie
2024-12-30 15:59   ` [PATCH v4 3/3] drivers/net: " Andre Muezerie
2024-12-30 17:44   ` [PATCH v4 0/3] " Stephen Hemminger
2024-12-31 18:55 ` [PATCH v5 " Andre Muezerie
2024-12-31 18:55   ` [PATCH v5 1/3] lib/eal: " Andre Muezerie
2024-12-31 18:55   ` [PATCH v5 2/3] drivers/common: " Andre Muezerie
2024-12-31 18:55   ` [PATCH v5 3/3] drivers/net: " Andre Muezerie
2024-12-31 20:15 ` [PATCH v6 0/3] " Andre Muezerie
2024-12-31 20:15   ` [PATCH v6 1/3] lib/eal: " Andre Muezerie
2024-12-31 20:15   ` [PATCH v6 2/3] drivers/common: " Andre Muezerie
2024-12-31 20:15   ` [PATCH v6 3/3] drivers/net: " Andre Muezerie
2024-12-31 22:30 ` [PATCH v7 0/3] " Andre Muezerie
2024-12-31 22:30   ` [PATCH v7 1/3] lib/eal: " Andre Muezerie
2024-12-31 22:30   ` [PATCH v7 2/3] drivers/common: " Andre Muezerie
2024-12-31 22:30   ` [PATCH v7 3/3] drivers/net: " Andre Muezerie
2025-01-01  0:48 ` [PATCH v8 0/3] " Andre Muezerie
2025-01-01  0:48   ` [PATCH v8 1/3] lib/eal: " Andre Muezerie
2025-01-01  0:48   ` [PATCH v8 2/3] drivers/common: " Andre Muezerie
2025-01-01  0:48   ` [PATCH v8 3/3] drivers/net: " Andre Muezerie
2025-01-01  3:36 ` [PATCH v9 0/3] " Andre Muezerie
2025-01-01  3:36   ` [PATCH v9 1/3] lib/eal: " Andre Muezerie
2025-01-01  3:36   ` [PATCH v9 2/3] drivers/common: " Andre Muezerie
2025-01-01  3:36   ` [PATCH v9 3/3] drivers/net: " Andre Muezerie
2025-01-03  0:12 ` [PATCH v10 0/3] " Andre Muezerie
2025-01-03  0:12   ` [PATCH v10 1/3] lib/eal: " Andre Muezerie
2025-01-03  0:12   ` [PATCH v10 2/3] drivers/common: " Andre Muezerie
2025-01-03  0:12   ` [PATCH v10 3/3] drivers/net: " Andre Muezerie
2025-01-03 15:36 ` [PATCH v11 0/3] " Andre Muezerie
2025-01-03 15:36   ` [PATCH v11 1/3] lib/eal: " Andre Muezerie
2025-01-03 15:36   ` [PATCH v11 2/3] drivers/common: " Andre Muezerie
2025-01-03 15:36   ` [PATCH v11 3/3] drivers/net: " Andre Muezerie
2025-01-03 19:24   ` [PATCH v11 0/3] " Stephen Hemminger
2025-01-03 21:26     ` Andre Muezerie
2025-01-06 11:00       ` Bruce Richardson
2025-01-08  2:46         ` Andre Muezerie
2025-01-08  9:20           ` Bruce Richardson
2025-01-14 19:20             ` Andre Muezerie
2025-01-15 11:11               ` Bruce Richardson
2025-01-15  4:27 ` [PATCH v12 " Andre Muezerie
2025-01-15  4:27   ` [PATCH v12 1/3] lib/eal: " Andre Muezerie
2025-01-15  9:05     ` Morten Brørup
2025-01-15  4:27   ` [PATCH v12 2/3] drivers/common: " Andre Muezerie
2025-01-15 11:13     ` Bruce Richardson
2025-01-15  4:27   ` [PATCH v12 3/3] drivers/net: " Andre Muezerie
2025-01-16  1:55 ` [PATCH v13 0/3] " Andre Muezerie
2025-01-16  1:55   ` [PATCH v13 1/3] eal: " Andre Muezerie
2025-01-16  1:55   ` [PATCH v13 2/3] drivers/common: " Andre Muezerie
2025-01-16  1:55   ` [PATCH v13 3/3] drivers/net: " Andre Muezerie
2025-01-16  8:57     ` Bruce Richardson
2025-01-16  9:08     ` Morten Brørup
2025-01-16  8:58   ` Bruce Richardson [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=Z4jKHaI4hMFCRFUN@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=andremue@linux.microsoft.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).