From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Steve Yang <stevex.yang@intel.com>
Cc: stable@dpdk.org, haiyue.wang@intel.com
Subject: Re: [PATCH 19.11] net/ice: build failure with make and GCC > 11
Date: Thu, 13 Jan 2022 08:57:27 +0100 [thread overview]
Message-ID: <CAATJJ0L87ZMTBDDWuKtysndruYMbPP4SWryN0PN4Pom_qg_c-A@mail.gmail.com> (raw)
In-Reply-To: <20220112064505.2182485-1-stevex.yang@intel.com>
On Wed, Jan 12, 2022 at 7:50 AM Steve Yang <stevex.yang@intel.com> wrote:
>
> Since GCC version is greater than 11.1.1, the '-finline-functions'
> option perhaps causes '-Werror=maybe-uninitialized' issue.
>
> Check the gcc version, and enable '-Wno-maybe-uninitialized',
> otherwise it will have "error: ‘r_bitmap’ may be used uninitialized".
Indeed the extended inlining might cause more detection of an issue like this.
Just disabling that warning for ICE will not make it worse, although unless that
detection is a false positive if there is a real fix to it avoiding
the dangerous
situation that would be even better.
For now I have queued the patch for 19.11.12
> Bugzilla ID: 744
>
> Signed-off-by: Steve Yang <stevex.yang@intel.com>
> ---
> drivers/net/ice/Makefile | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/net/ice/Makefile b/drivers/net/ice/Makefile
> index 6c4d155268..07044d6ed7 100644
> --- a/drivers/net/ice/Makefile
> +++ b/drivers/net/ice/Makefile
> @@ -34,6 +34,10 @@ ifeq ($(shell test $(GCC_VERSION) -ge 44 && echo 1), 1)
> CFLAGS_BASE_DRIVER += -Wno-unused-but-set-variable
> endif
>
> +ifeq ($(shell test $(GCC_VERSION) -ge 110 && echo 1), 1)
> +CFLAGS_BASE_DRIVER += -Wno-maybe-uninitialized
> +endif
> +
> endif
> OBJS_BASE_DRIVER=$(patsubst %.c,%.o,$(notdir $(wildcard $(SRCDIR)/base/*.c)))
> $(foreach obj, $(OBJS_BASE_DRIVER), $(eval CFLAGS_$(obj)+=$(CFLAGS_BASE_DRIVER)))
> --
> 2.27.0
>
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2022-01-13 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 6:45 Steve Yang
2022-01-13 7:57 ` Christian Ehrhardt [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=CAATJJ0L87ZMTBDDWuKtysndruYMbPP4SWryN0PN4Pom_qg_c-A@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=haiyue.wang@intel.com \
--cc=stable@dpdk.org \
--cc=stevex.yang@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).