DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Zhichao Zeng <zhichaox.zeng@intel.com>
Cc: dev@dpdk.org, qi.z.zhang@intel.com, daxuex.gao@intel.com,
	 Bruce Richardson <bruce.richardson@intel.com>,
	 Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
	Jingjing Wu <jingjing.wu@intel.com>,
	 Beilei Xing <beilei.xing@intel.com>,
	Wenjun Wu <wenjun1.wu@intel.com>
Subject: Re: [PATCH] net/iavf: fix old GCC compilation warnings
Date: Fri, 9 Jun 2023 08:58:15 +0200	[thread overview]
Message-ID: <CAJFAV8y9F6ARpXEtZQnjVUjy5KMFSwvf0WJNhNMpQ+zWna2cGw@mail.gmail.com> (raw)
In-Reply-To: <20230609054156.605581-1-zhichaox.zeng@intel.com>

On Fri, Jun 9, 2023 at 7:35 AM Zhichao Zeng <zhichaox.zeng@intel.com> wrote:
>
> The code uses the Wimplicit-fallthrough compile option to ignore
> falls through warnings in switch case, but this option was introduced
> by GCC 7 and old GCC do not recognize the option.
>
> Add judgment to avoid warnings about unrecognized options in old GCC.
>
> Fixes: 95a1b0b23140 ("net/iavf: support Rx timestamp offload on SSE")
> Fixes: 4f58266da4d3 ("net/iavf: support Rx timestamp offload on AVX2")
> Fixes: d65eadb9e178 ("net/iavf: support Rx timestamp offload on AVX512")
> Signed-off-by: Zhichao Zeng <zhichaox.zeng@intel.com>

This is ugly.

I don't think we introduced a marker for this in EAL, but at least I
see other drivers use /* fallthrough */.
Prefer this form, please.

IOW:

diff --git a/drivers/net/iavf/iavf_rxtx_vec_sse.c
b/drivers/net/iavf/iavf_rxtx_vec_sse.c
index b754122c51..81ea154519 100644
--- a/drivers/net/iavf/iavf_rxtx_vec_sse.c
+++ b/drivers/net/iavf/iavf_rxtx_vec_sse.c
@@ -1126,24 +1126,26 @@ _recv_raw_pkts_vec_flex_rxd(struct iavf_rx_queue *rxq,
                nb_pkts_recd += var;

 #ifndef RTE_LIBRTE_IAVF_16BYTE_RX_DESC
-#pragma GCC diagnostic push
-#pragma GCC diagnostic ignored "-Wimplicit-fallthrough"
                if (rxq->offloads & RTE_ETH_RX_OFFLOAD_TIMESTAMP) {
                        inflection_point = (inflection_point <= var) ?
inflection_point : 0;
                        switch (inflection_point) {
                        case 1:
                                *RTE_MBUF_DYNFIELD(rx_pkts[pos + 0],
                                        iavf_timestamp_dynfield_offset
+ 4, uint32_t *) += 1;
+                               /* fallthrough */
                        case 2:

etc...


-- 
David Marchand


  reply	other threads:[~2023-06-09  6:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  5:41 Zhichao Zeng
2023-06-09  6:58 ` David Marchand [this message]
2023-06-09  7:19   ` Zeng, ZhichaoX
2023-06-09  9:02 ` [PATCH v2] net/iavf: fix " Zhichao Zeng
2023-06-12  8:32   ` Gao, DaxueX
2023-06-12  9:01     ` Thomas Monjalon
2023-06-12 12:29       ` Zhang, Qi Z
2023-06-12 14:15         ` Thomas Monjalon
2023-06-12 15:08           ` Zhang, Qi Z
2023-06-09 14:38 ` [PATCH] net/iavf: fix old GCC " Stephen Hemminger

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=CAJFAV8y9F6ARpXEtZQnjVUjy5KMFSwvf0WJNhNMpQ+zWna2cGw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=beilei.xing@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=daxuex.gao@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=qi.z.zhang@intel.com \
    --cc=wenjun1.wu@intel.com \
    --cc=zhichaox.zeng@intel.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).