DPDK patches and discussions
 help / color / mirror / Atom feed
From: Joyce Kong <Joyce.Kong@arm.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: "reshma.pattan@intel.com" <reshma.pattan@intel.com>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>,
	"konstantin.v.ananyev@yandex.ru" <konstantin.v.ananyev@yandex.ru>,
	"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Ruifeng Wang <Ruifeng.Wang@arm.com>
Subject: RE: [PATCH] pdump: fix build issue with GCC 12
Date: Tue, 28 Mar 2023 06:27:07 +0000	[thread overview]
Message-ID: <AS4PR08MB7712078197C8CE8A7AB37A3E92889@AS4PR08MB7712.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20230327143439.GB26463@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>

> -----Original Message-----
> From: Tyler Retzlaff <roretzla@linux.microsoft.com>
> Sent: Monday, March 27, 2023 10:35 PM
> To: Joyce Kong <Joyce.Kong@arm.com>
> Cc: reshma.pattan@intel.com; stephen@networkplumber.org;
> konstantin.v.ananyev@yandex.ru; dev@dpdk.org; nd <nd@arm.com>;
> stable@dpdk.org; Ruifeng Wang <Ruifeng.Wang@arm.com>
> Subject: Re: [PATCH] pdump: fix build issue with GCC 12
> 
> On Mon, Mar 27, 2023 at 07:07:12AM +0000, Joyce Kong wrote:
> > The following warning is observed with GCC12 compilation with release
> > 20.11:
> >
> > In function ‘__rte_ring_enqueue_elems_64’,
> >     inlined from ‘__rte_ring_enqueue_elems’ at
> >             ../lib/librte_ring/rte_ring_elem.h:225:3,
> >     inlined from ‘__rte_ring_do_enqueue_elem’ at
> >             ../lib/librte_ring/rte_ring_elem.h:424:2,
> >     inlined from ‘rte_ring_mp_enqueue_burst_elem’ at
> >             ../lib/librte_ring/rte_ring_elem.h:884:9,
> >     inlined from ‘rte_ring_enqueue_burst_elem’ at
> >             ../lib/librte_ring/rte_ring_elem.h:946:10,
> >     inlined from ‘rte_ring_enqueue_burst’ at
> >             ../lib/librte_ring/rte_ring.h:721:9,
> >     inlined from ‘pdump_copy’ at
> >             ../lib/librte_pdump/rte_pdump.c:94:13:
> > ../lib/librte_ring/rte_ring_elem.h:162:40: warning: ‘*dup_bufs.36_42
> > + _89’ may be used uninitialized [-Wmaybe-uninitialized]
> >   162 |                         ring[idx] = obj[i];
> >       |                                     ~~~^~~
> > ../lib/librte_ring/rte_ring_elem.h:163:44: warning: ‘*dup_bufs.36_42
> > + _98’ may be used uninitialized [-Wmaybe-uninitialized]
> >   163 |                         ring[idx + 1] = obj[i + 1];
> >       |                                         ~~~^~~~~~~
> > ../lib/librte_ring/rte_ring_elem.h:164:44: warning: ‘*dup_bufs.36_42
> > + _107’ may be used uninitialized [-Wmaybe-uninitialized]
> >   164 |                         ring[idx + 2] = obj[i + 2];
> >       |                                         ~~~^~~~~~~
> > ../lib/librte_ring/rte_ring_elem.h:165:44: warning: ‘*dup_bufs.36_42
> > + _116’ may be used uninitialized [-Wmaybe-uninitialized]
> >   165 |                         ring[idx + 3] = obj[i + 3];
> >       |                                         ~~~^~~~~~~
> > ../lib/librte_ring/rte_ring_elem.h:169:42: warning: ‘*dup_bufs.36_42
> > + _129’ may be used uninitialized [-Wmaybe-uninitialized]
> >   169 |                         ring[idx++] = obj[i++]; /* fallthrough */
> >       |                                       ~~~^~~~~
> > ../lib/librte_ring/rte_ring_elem.h:171:42: warning: ‘*dup_bufs.36_42
> > + _139’ may be used uninitialized [-Wmaybe-uninitialized]
> >   171 |                         ring[idx++] = obj[i++]; /* fallthrough */
> >       |                                       ~~~^~~~~
> > ../lib/librte_ring/rte_ring_elem.h:173:42: warning: ‘*dup_bufs.36_42
> > + _149’ may be used uninitialized [-Wmaybe-uninitialized]
> >   173 |                         ring[idx++] = obj[i++];
> >
> > 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.
> >
> > Fixes: 278f945402c5 ("pdump: add new library for packet capture")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Joyce Kong <joyce.kong@arm.com>
> > Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> > ---
> 
> Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> 
> >  lib/pdump/rte_pdump.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lib/pdump/rte_pdump.c b/lib/pdump/rte_pdump.c index
> > 9bc4bab4f2..53cca1034d 100644
> > --- a/lib/pdump/rte_pdump.c
> > +++ b/lib/pdump/rte_pdump.c
> > @@ -134,7 +134,7 @@ pdump_copy(uint16_t port_id, uint16_t queue,
> >
> >  	__atomic_fetch_add(&stats->accepted, d_pkts, __ATOMIC_RELAXED);
> >
> > -	ring_enq = rte_ring_enqueue_burst(ring, (void *)dup_bufs, d_pkts,
> NULL);
> > +	ring_enq = rte_ring_enqueue_burst(ring, (void *)&dup_bufs[0],
> > +d_pkts, NULL);
> 
> nit: i would drop the cast to void *, it shouldn't be needed?

Removing 'void *' here would generate a warning from incompatible pointer type, 
as rte_ring_enqueue_burst(struct rte_ring *r, void * const *obj_table, ...) expected 
'void * const *', but argument of &dup_bufs[0] is of type 'struct rte_mbuf **'. 

  reply	other threads:[~2023-03-28  6:27 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 [this message]
2023-03-28 16:25 ` Thomas Monjalon
2023-03-28 19:25 ` 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=AS4PR08MB7712078197C8CE8A7AB37A3E92889@AS4PR08MB7712.eurprd08.prod.outlook.com \
    --to=joyce.kong@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=nd@arm.com \
    --cc=reshma.pattan@intel.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.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).