From: Stephen Hemminger <stephen@networkplumber.org>
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 07:38:42 -0700 [thread overview]
Message-ID: <20230609073842.597ae326@hermes.local> (raw)
In-Reply-To: <20230609054156.605581-1-zhichaox.zeng@intel.com>
On Fri, 9 Jun 2023 13:41:56 +0800
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>
> ---
RHEL 7 becomes end of life this month.
That makes the oldest version of Gcc that DPDK is required to support
is gcc 8.X in RHEL 8.
prev parent reply other threads:[~2023-06-09 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 5:41 [PATCH] net/iavf: fix old GCC compilation warnings Zhichao Zeng
2023-06-09 6:58 ` David Marchand
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 ` Stephen Hemminger [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=20230609073842.597ae326@hermes.local \
--to=stephen@networkplumber.org \
--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).