public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, Amit Machhiwal <amachhiw@linux.ibm.com>
Cc: Vaibhav Jain <vaibhav@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Christophe Leroy <chleroy@kernel.org>,
	Shuah Khan <shuah@kernel.org>, Greg Kurz <groug@kaod.org>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2] selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15
Date: Wed,  8 Apr 2026 09:58:17 +0530	[thread overview]
Message-ID: <177562236422.1381144.4554144401168873566.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260313165426.43259-1-amachhiw@linux.ibm.com>

On Fri, 13 Mar 2026 22:24:26 +0530, Amit Machhiwal wrote:
> GCC 15 reports the below false positive '-Wmaybe-uninitialized' warning
> in vphn_unpack_associativity() when building the powerpc selftests.
> 
>   # make -C tools/testing/selftests TARGETS="powerpc"
>   [...]
>     CC       test-vphn
>   In file included from test-vphn.c:3:
>   In function ‘vphn_unpack_associativity’,
>       inlined from ‘test_one’ at test-vphn.c:371:2,
>       inlined from ‘test_vphn’ at test-vphn.c:399:9:
>   test-vphn.c:10:33: error: ‘be_packed’ may be used uninitialized [-Werror=maybe-uninitialized]
>      10 | #define be16_to_cpup(x)         bswap_16(*x)
>         |                                 ^~~~~~~~
>   vphn.c:42:27: note: in expansion of macro ‘be16_to_cpup’
>      42 |                 u16 new = be16_to_cpup(field++);
>         |                           ^~~~~~~~~~~~
>   In file included from test-vphn.c:19:
>   vphn.c: In function ‘test_vphn’:
>   vphn.c:27:16: note: ‘be_packed’ declared here
>      27 |         __be64 be_packed[VPHN_REGISTER_COUNT];
>         |                ^~~~~~~~~
>   cc1: all warnings being treated as errors
> 
> [...]

Applied to powerpc/next.

[1/1] selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15
      https://git.kernel.org/powerpc/c/6e65886fceb23605eff952d6b1975737b4c4b154

cheers


      parent reply	other threads:[~2026-04-08  4:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 16:54 [PATCH v2] selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 Amit Machhiwal
2026-03-13 17:11 ` Venkat
2026-04-08  4:28 ` Madhavan Srinivasan [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=177562236422.1381144.4554144401168873566.b4-ty@linux.ibm.com \
    --to=maddy@linux.ibm.com \
    --cc=amachhiw@linux.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=groug@kaod.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=shuah@kernel.org \
    --cc=vaibhav@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox