From: Segher Boessenkool <segher@kernel.crashing.org>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: nathan@kernel.org, ndesaulniers@google.com, mpe@ellerman.id.au,
Arnd Bergmann <arnd@arndb.de>,
llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCHv3, resend] powerpc: mm: radix_tlb: rearrange the if-else block
Date: Wed, 10 Aug 2022 08:56:21 -0500 [thread overview]
Message-ID: <20220810135621.GX25951@gate.crashing.org> (raw)
In-Reply-To: <20220810114318.3220630-1-anders.roxell@linaro.org>
Hi!
On Wed, Aug 10, 2022 at 01:43:18PM +0200, Anders Roxell wrote:
> Clang warns:
>
> arch/powerpc/mm/book3s64/radix_tlb.c:1191:23: error: variable 'hstart' is uninitialized when used here [-Werror,-Wuninitialized]
> __tlbiel_va_range(hstart, hend, pid,
> ^~~~~~
> arch/powerpc/mm/book3s64/radix_tlb.c:1175:23: note: initialize the variable 'hstart' to silence this warning
This note often is bad advice: hiding problems instead of investigating
and solving them. Bah.
If silencing warnings is your goal, look no further than "-w" :-)
> Rework the 'if (IS_ENABLE(CONFIG_TRANSPARENT_HUGEPAGE))' so hstart/hend
> always gets initialized, this will silence the warnings. That will also
> simplify the 'else' path. Clang is getting confused with these warnings,
> but the warnings is a false-positive.
If it is, please report that bug to clang? It says "*is* uninitialized
when used here", there can not be false positives to statements like
that. If the analysis was heutistical it should say "may be" or such.
Segher
next prev parent reply other threads:[~2022-08-10 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 11:43 [PATCHv3, resend] powerpc: mm: radix_tlb: rearrange the if-else block Anders Roxell
2022-08-10 13:56 ` Segher Boessenkool [this message]
2022-08-11 9:41 ` Michael Ellerman
2022-08-11 12:35 ` Anders Roxell
2023-02-20 3:49 ` Michael Ellerman
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=20220810135621.GX25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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