From: Dave Haywood <tla@oak.selfip.net>
To: Borislav Petkov <bp@alien8.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Build warning: kernel/trace/trace.c (v3.2-rc1-90-g19e0baf)
Date: Thu, 10 Nov 2011 01:11:07 +0000 [thread overview]
Message-ID: <4EBB24AB.3090307@oak.selfip.net> (raw)
In-Reply-To: <20111109113303.GA18508@gere.osrc.amd.com>
On 09/11/2011 11:33, Borislav Petkov wrote:
> On Wed, Nov 09, 2011 at 08:47:58AM +0000, Dave Haywood wrote:
>> Hi,
>>
>> Noticed this new warning in the build of kernel v3.2-rc1-90-g19e0baf:
>>
>> CC kernel/trace/trace.o
>> kernel/trace/trace.c: In function 'tracing_mark_write':
>> kernel/trace/trace.c:3644:8: warning: 'page2' may be used uninitialized in this function
> That has to be gcc 4.5.x something. 4.6 is smarter in that aspect:
Correct, version is:
$ gcc --version
gcc (Gentoo Hardened 4.5.3-r1 p1.0, pie-0.4.5) 4.5.3
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> $ make CC=gcc-4.6 kernel/trace/trace.o
> CHK include/linux/version.h
> UPD include/linux/version.h
> CHK include/generated/utsrelease.h
> UPD include/generated/utsrelease.h
> CC kernel/bounds.s
>
> ...
>
> HOSTLD scripts/mod/modpost
> CC kernel/trace/trace.o
> $ make CC=gcc-4.5 kernel/trace/trace.o
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> CC kernel/bounds.s
>
> ...
>
> HOSTLD scripts/mod/modpost
> CC kernel/trace/trace.o
> kernel/trace/trace.c: In function ‘tracing_mark_write’:
> kernel/trace/trace.c:3644:8: warning: ‘page2’ may be used uninitialized in this function
>
> HTH
>
prev parent reply other threads:[~2011-11-10 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 8:47 Build warning: kernel/trace/trace.c (v3.2-rc1-90-g19e0baf) Dave Haywood
2011-11-09 11:33 ` Borislav Petkov
2011-11-10 1:11 ` Dave Haywood [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=4EBB24AB.3090307@oak.selfip.net \
--to=tla@oak.selfip.net \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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