From: Stephen Hemminger <stephen@networkplumber.org>
To: Joyce Kong <joyce.kong@arm.com>
Cc: reshma.pattan@intel.com, konstantin.v.ananyev@yandex.ru,
dev@dpdk.org, nd@arm.com, stable@dpdk.org,
Ruifeng Wang <ruifeng.wang@arm.com>
Subject: Re: [PATCH] pdump: fix build issue with GCC 12
Date: Tue, 28 Mar 2023 12:25:06 -0700 [thread overview]
Message-ID: <20230328122506.340e58ba@hermes.local> (raw)
In-Reply-To: <20230327070712.280265-1-joyce.kong@arm.com>
On Mon, 27 Mar 2023 07:07:12 +0000
Joyce Kong <joyce.kong@arm.com> wrote:
> Actually, this is an alias warning as -O3 enables strict alias.
> This patch fixes it by replacing 'dup_bufs' with '&dup_bufs[0]'
> as the compiler represents them differently.
This looks more like a compiler bug, since both should be
equivalent in C.
prev parent reply other threads:[~2023-03-28 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 7:07 Joyce Kong
2023-03-27 14:19 ` Pattan, Reshma
2023-03-27 14:34 ` Tyler Retzlaff
2023-03-28 6:27 ` Joyce Kong
2023-03-28 16:25 ` Thomas Monjalon
2023-03-28 19:25 ` 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=20230328122506.340e58ba@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=joyce.kong@arm.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=nd@arm.com \
--cc=reshma.pattan@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=stable@dpdk.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).