Re: [PATCH] hash: fix maybe-uninitialized warnings on build

[Bruce Richardson <bruce.richardson@intel.com>]

On Thu, Feb 12, 2026 at 05:54:22PM +0100, David Marchand wrote:
> 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>
> 
I don't think any of the CIs use the test-meson-build scripts, do they?
It's more a convenience for maintainers.