From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
natechancellor@gmail.com, ndesaulniers@google.com,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] mips: lib: uncached: fix uninitialized variable 'sp'
Date: Sun, 6 Dec 2020 09:36:16 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.2012060915460.656242@eddie.linux-mips.org> (raw)
In-Reply-To: <20201127083938.2666770-1-anders.roxell@linaro.org>
On Fri, 27 Nov 2020, Anders Roxell wrote:
> When building mips tinyconfig with clang the following warning show up:
>
> /tmp/arch/mips/lib/uncached.c:40:18: note: initialize the variable 'sp' to silence this warning
> register long sp __asm__("$sp");
> ^
> = 0
>
> Rework to make an explicit inline move.
It's not uninitialised, because by definition $sp has been initialised.
This code wouldn't have worked for the last 15 years otherwise.
It is however non-standard usage (which may not have been clarified at
the time this piece was made; I recall extensive discussions around this
feature over the years):
"6.47.5.2 Specifying Registers for Local Variables
.................................................
[...]
"The only supported use for this feature is to specify registers for
input and output operands when calling Extended 'asm' (*note Extended
Asm::). [...]"
so the change description should refer to that as the rationale rather
than an implementation-specific misleading warning (although that can be
quoted for a reference of course).
> diff --git a/arch/mips/lib/uncached.c b/arch/mips/lib/uncached.c
> index 09d5deea747f..21a4b94a0558 100644
> --- a/arch/mips/lib/uncached.c
> +++ b/arch/mips/lib/uncached.c
> @@ -37,10 +37,11 @@
> */
> unsigned long run_uncached(void *func)
> {
> - register long sp __asm__("$sp");
> register long ret __asm__("$2");
> long lfunc = (long)func, ufunc;
> long usp;
> + long sp;
> + asm ("move %0, $sp" : "=r" (sp));
Missing newline between the variable block and code here; you may well
swap it with the empty line below you have left. Also use `__asm__' for
consistency, and remove the extraneous space ahead of the parenthesis as
we don't use them in Linux. Using a tab to separate the mnemonic from
operands is also preferable, i.e. "move\t%0, $sp" in this case (using
actual tabs works better with multi-line assembly, but this is not one).
I think this should be OK once the issues I mentioned here have been
addressed.
Maciej
next prev parent reply other threads:[~2020-12-06 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 8:39 [PATCH] mips: lib: uncached: fix uninitialized variable 'sp' Anders Roxell
2020-11-30 20:22 ` Nick Desaulniers
2020-12-01 0:50 ` Anders Roxell
2020-12-06 9:36 ` Maciej W. Rozycki [this message]
2020-12-06 14:33 ` Maciej W. Rozycki
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=alpine.LFD.2.21.2012060915460.656242@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=anders.roxell@linaro.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for NNTP newsgroup(s).