From: "Figo.zhang" <figo1802@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]io_apic.c: fix compile warning
Date: Wed, 17 Jun 2009 22:29:18 +0800 [thread overview]
Message-ID: <1245248958.3312.28.camel@myhost> (raw)
In-Reply-To: <20090617152846.72804bae@lxorguk.ukuu.org.uk>
On Wed, 2009-06-17 at 15:28 +0100, Alan Cox wrote:
> On Wed, 17 Jun 2009 22:25:20 +0800
> "Figo.zhang" <figo1802@gmail.com> wrote:
>
> > fix compile warning:
> > arch/x86/kernel/apic/io_apic.c: In function ‘ioapic_write_entry’:
> > arch/x86/kernel/apic/io_apic.c:466: warning: ‘eu’ is used uninitialized in this function
> > arch/x86/kernel/apic/io_apic.c:465: note: ‘eu’ was declared here
>
> What compiler are you using. Current gcc correctly notices that there are
> no uninitialized things to worry about ?
hi Alan:
my gcc is:
[figo@myhost linux-2.6]$ gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../configure --prefix=/usr --enable-shared
--enable-languages=c,c++,fortran,objc,obj-c++ --enable-threads=posix
--mandir=/usr/share/man --infodir=/usr/share/info --enable-__cxa_atexit
--disable-multilib --libdir=/usr/lib --libexecdir=/usr/lib
--enable-clocale=gnu --disable-libstdcxx-pch --with-tune=generic
Thread model: posix
gcc version 4.4.0 20090526 (prerelease) (GCC)
[figo@myhost linux-2.6]$
Best Regards,
Figo.zhang
next prev parent reply other threads:[~2009-06-17 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 14:25 [PATCH]io_apic.c: fix compile warning Figo.zhang
2009-06-17 14:28 ` Alan Cox
2009-06-17 14:29 ` Figo.zhang [this message]
[not found] ` <bb33bcf20906170729n616dcdbfkc02a168347612138@mail.gmail.com>
2009-06-17 14:35 ` Subrata Modak
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=1245248958.3312.28.camel@myhost \
--to=figo1802@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.