From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alexander Graf <agraf@suse.de>
Cc: Avi Kivity <avi@qumranet.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: kvm tree build warning
Date: Thu, 21 Jan 2010 00:01:28 +1100 [thread overview]
Message-ID: <20100121000128.cf11525c.sfr@canb.auug.org.au> (raw)
In-Reply-To: <3727B46C-0197-47A4-AF41-023517C15752@suse.de>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
Hi Alex,
On Wed, 20 Jan 2010 11:42:28 +0100 Alexander Graf <agraf@suse.de> wrote:
>
> This is odd. The same function saves and restores ext_bkp.vrsave under a common condition:
>
> So there can't be a case where ext_bkp.vrsave is read, but not written to before, which is what this warning implies, right?
Right.
> Also, why doesn't gcc complain about vscr too then? They're both used in the very same if statement.
I have no idea how gcc makes these decisions. :-(
> Additionally, while compiling locally I looked for warnings and didn't spot any. So apparently our compiler versions / options don't match. Which version of gcc are you using? I assume a gcc bug.
>
> $ gcc --version
> gcc (SUSE Linux) 4.3.2 [gcc-4_3-branch revision 141291]
I use a 4.4.0 cross compiler (I should update it).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-20 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 6:48 linux-next: kvm tree build warning Stephen Rothwell
2010-01-20 10:42 ` Alexander Graf
2010-01-20 13:01 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-20 6:38 Stephen Rothwell
2010-01-11 8:25 Stephen Rothwell
2009-07-06 1:37 Stephen Rothwell
2009-07-06 5:28 ` Gleb Natapov
2009-07-06 6:01 ` Stephen Rothwell
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=20100121000128.cf11525c.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agraf@suse.de \
--cc=avi@qumranet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mtosatti@redhat.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