From: David Marchand <david.marchand@redhat.com>
To: Wenxuan Wu <wenxuanx.wu@intel.com>
Cc: Qiming Yang <qiming.yang@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>, dev <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>,
dpdk stable <stable@dpdk.org>
Subject: Re: [PATCH] ice/base: fix gcc 12 warning stringop-overflow
Date: Thu, 16 Jun 2022 16:29:15 +0200 [thread overview]
Message-ID: <CAJFAV8zCCNuSxjSp3q+_h52LiJYik4EjDhy5CW8gG9KBUB=djw@mail.gmail.com> (raw)
In-Reply-To: <20220616103304.132368-1-wenxuanx.wu@intel.com>
Title should start with net/ice/base:.
On Thu, Jun 16, 2022 at 12:35 PM <wenxuanx.wu@intel.com> wrote:
>
> From: Wenxuan Wu <wenxuanx.wu@intel.com>
>
> Gcc with -O2 flag, would retrieve the value in one time.
> This patch changed the type of fv_idx in struct ice_recp_grp_entry to
> align with its callers which is also u8 type.
>
> When u8 idx[5] = a value u16 index[4], gcc12 would give this warning,
> because it is not big enough to store the bytes(bigger than 5 bytes)
> in one time (-O2 would do it in this way).
>
> Fixes: 04b8ec1ea807 ("net/ice/base: add protocol structures and defines")
> Cc: stable@dpdk.org
Missing empty line.
> Signed-off-by: Wenxuan Wu <wenxuanx.wu@intel.com>
Only build tested.
Tested-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
next prev parent reply other threads:[~2022-06-16 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 10:33 [PATCH] ice/base: fix gcc 12 warning stringop-overflow wenxuanx.wu
2022-06-16 14:29 ` David Marchand [this message]
2022-06-17 1:29 ` Wu, WenxuanX
2022-06-17 5:04 ` David Marchand
2022-06-19 12:34 ` Zhang, Qi Z
2022-06-20 1:38 ` Wu, WenxuanX
2022-06-20 5:06 ` Wu, WenxuanX
2022-06-23 7:42 ` David Marchand
2022-06-23 9:01 ` [PATCH v2] net/ice/base: " wenxuanx.wu
2022-06-23 9:21 ` Zhang, Qi Z
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='CAJFAV8zCCNuSxjSp3q+_h52LiJYik4EjDhy5CW8gG9KBUB=djw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=wenxuanx.wu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.