From: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>, <dev@dpdk.org>
Cc: <stable@dpdk.org>
Subject: Re: [PATCH] hash: fix maybe-uninitialized warnings on build
Date: Thu, 12 Feb 2026 16:44:16 +0000 [thread overview]
Message-ID: <97685f05-c5a6-488b-b67f-f65dbf5e97af@intel.com> (raw)
In-Reply-To: <20260212162705.3923717-1-bruce.richardson@intel.com>
Acked-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
On 2/12/2026 4:27 PM, Bruce Richardson 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>
> ---
> lib/hash/rte_thash_x86_gfni.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/hash/rte_thash_x86_gfni.h b/lib/hash/rte_thash_x86_gfni.h
> index 99226b7592..69973503fd 100644
> --- a/lib/hash/rte_thash_x86_gfni.h
> +++ b/lib/hash/rte_thash_x86_gfni.h
> @@ -89,9 +89,9 @@ __rte_thash_gfni(const uint64_t *mtrx, const uint8_t *tuple,
> const __m512i shift_8 = _mm512_set1_epi8(8);
> __m512i xor_acc = _mm512_setzero_si512();
> __m512i perm_bytes = _mm512_setzero_si512();
> - __m512i vals, matrixes, tuple_bytes_2;
> + __m512i vals, matrixes, tuple_bytes_2 = _mm512_setzero_si512();
> __m512i tuple_bytes = _mm512_setzero_si512();
> - __mmask64 load_mask, permute_mask_2;
> + __mmask64 load_mask, permute_mask_2 = 0;
> __mmask64 permute_mask = 0;
> int chunk_len = 0, i = 0;
> uint8_t mtrx_msk;
--
Regards,
Vladimir
next prev parent reply other threads:[~2026-02-12 16:44 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 [this message]
2026-02-12 16:54 ` David Marchand
2026-02-12 17:01 ` Bruce Richardson
2026-02-13 18:22 ` Thomas Monjalon
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=97685f05-c5a6-488b-b67f-f65dbf5e97af@intel.com \
--to=vladimir.medvedkin@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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