From: David Daney <ddaney@caviumnetworks.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Cong Ding <dinggnu@gmail.com>, Jim Quinlan <jim2101024@gmail.com>,
<linux-mips@linux-mips.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mpis: cavium-octeon/executive/cvmx-l2c.c: fix uninitialized variable
Date: Wed, 16 Jan 2013 09:56:03 -0800 [thread overview]
Message-ID: <50F6E9B3.5010202@caviumnetworks.com> (raw)
In-Reply-To: <20130116105757.GB26569@linux-mips.org>
On 01/16/2013 02:57 AM, Ralf Baechle wrote:
> On Mon, Jan 14, 2013 at 10:47:03PM +0100, Cong Ding wrote:
>
>> the variable dummy is used without initialization.
>
> Interesting - I wonder how you found this one. My compiler (gcc 4.7)
> doesn't warn about this one.
>
I get no warnings either. So I wonder what the point of churning up the
code is.
David Daney
> Nor does gcc notice that the whole summing up business is wasted efford.
>
> So here's my counter proposal. It works because ptr is a volatile pointer
> so the compiler will always dereference it even if the returned value is
> not being used. The resulting code is a bit smaller.
>
> Ralf
>
> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
>
> arch/mips/cavium-octeon/executive/cvmx-l2c.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/cavium-octeon/executive/cvmx-l2c.c b/arch/mips/cavium-octeon/executive/cvmx-l2c.c
> index 9f883bf..ec3e059 100644
> --- a/arch/mips/cavium-octeon/executive/cvmx-l2c.c
> +++ b/arch/mips/cavium-octeon/executive/cvmx-l2c.c
> @@ -286,7 +286,7 @@ uint64_t cvmx_l2c_read_perf(uint32_t counter)
> static void fault_in(uint64_t addr, int len)
> {
> volatile char *ptr;
> - volatile char dummy;
> +
> /*
> * Adjust addr and length so we get all cache lines even for
> * small ranges spanning two cache lines.
> @@ -300,7 +300,7 @@ static void fault_in(uint64_t addr, int len)
> */
> CVMX_DCACHE_INVALIDATE;
> while (len > 0) {
> - dummy += *ptr;
> + *ptr;
> len -= CVMX_CACHE_LINE_SIZE;
> ptr += CVMX_CACHE_LINE_SIZE;
> }
>
>
>
next prev parent reply other threads:[~2013-01-16 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 21:47 [PATCH] mpis: cavium-octeon/executive/cvmx-l2c.c: fix uninitialized variable Cong Ding
2013-01-16 10:57 ` Ralf Baechle
2013-01-16 17:56 ` David Daney [this message]
2013-01-16 18:09 ` Geert Uytterhoeven
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=50F6E9B3.5010202@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=dinggnu@gmail.com \
--cc=jim2101024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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