All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, vladimir.medvedkin@intel.com,
	David Marchand <david.marchand@redhat.com>,
	stable@dpdk.org
Subject: Re: [PATCH] hash: fix maybe-uninitialized warnings on build
Date: Fri, 13 Feb 2026 19:22:01 +0100	[thread overview]
Message-ID: <4193989.RQLdHFEMZ3@thomas> (raw)
In-Reply-To: <CAJFAV8xteqCnX7LKqPWFSmvbBz-rQVCRUuSmHLaHdG-BckhAqA@mail.gmail.com>

12/02/2026 17:54, David Marchand:
> On Thu, 12 Feb 2026 at 17:27, Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > Following recent changes to the test-meson-build.sh script[1] to use more
> > build-types warnings are seen in the hash library GFNI code about values
> > possibly being uninitialized.
> >
> > In function ‘_mm512_mask_permutexvar_epi8’,
> >     inlined from ‘__rte_thash_gfni’ at ../lib/hash/rte_thash_x86_gfni.h:150:6:
> > /usr/lib/gcc/x86_64-linux-gnu/15/include/avx512vbmiintrin.h:97:20: error: ‘tuple_bytes_2’ may be used uninitialized [-Werror=maybe-uninitialized]
> >
> > These all appear to be a false positive, but fix these by explicitly
> > zero-initializing the offending values.
> >
> > [1] 177acaf5cf75 ("devtools: test different build types")
> >
> > Fixes: 4fd8c4cb0de1 ("hash: add new Toeplitz hash implementation")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> 
> Too bad Intel CI did not catch it.
> 
> Acked-by: David Marchand <david.marchand@redhat.com>

Applied, thanks.




      parent reply	other threads:[~2026-02-13 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 16:27 [PATCH] hash: fix maybe-uninitialized warnings on build Bruce Richardson
2026-02-12 16:44 ` Medvedkin, Vladimir
2026-02-12 16:54 ` David Marchand
2026-02-12 17:01   ` Bruce Richardson
2026-02-13 18:22   ` Thomas Monjalon [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=4193989.RQLdHFEMZ3@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=vladimir.medvedkin@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.