From: Ian Campbell <ian.campbell@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: Ian Murray <murrayie@yahoo.co.uk>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Compliling Xen 4.5.0 Fails with error: ‘bufioreq_pfn’ may be used uninitialised in this function [-Werror=uninitialized]
Date: Mon, 16 Mar 2015 10:00:48 +0000 [thread overview]
Message-ID: <1426500048.18247.7.camel@citrix.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD0258434BF@AMSPEX01CL01.citrite.net>
On Mon, 2015-03-16 at 09:45 +0000, Paul Durrant wrote:
> Those line numbers don't work for me. I did a checkout of
> RELEASE-4.5.0 and, whilst bufioreq_pfn is indeed declared on line 718,
> I see no reference to it on line 487. Also, if I compile debug=n I see
> no problem. Is it possible you don't have a clean checkout of 4.5.0?
> What version of gcc are you using?
Doing
git show RELEASE-4.5.0:xen/arch/x86/hvm/hvm.c > x
gets me a file x where line 487 is the first line (defn of "i") of:
static void hvm_free_ioreq_gmfn(struct domain *d, unsigned long gmfn)
{
unsigned int i = gmfn - d->arch.hvm_domain.ioreq_gmfn.base;
clear_bit(i, &d->arch.hvm_domain.ioreq_gmfn.mask);
}
My guess was that it was the call from the fial3 label in
hvm_ioreq_server_map_pages(). I can see how gcc wouldn't always be able
to reason about it always being initialised.
Ian.
next prev parent reply other threads:[~2015-03-16 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1426264521.32572.176.camel@citrix.com>
[not found] ` <1430082348.3376440.1426266319145.JavaMail.yahoo@mail.yahoo.com>
2015-03-15 22:59 ` Compliling Xen 4.5.0 Fails with error: ‘bufioreq_pfn’ may be used uninitialised in this function [-Werror=uninitialized] Ian Murray
2015-03-16 9:45 ` Paul Durrant
2015-03-16 10:00 ` Ian Campbell [this message]
2015-03-16 21:19 ` Ian Murray
2015-03-17 0:10 ` Slutz, Donald Christopher
2015-03-17 1:07 ` Ian Murray
2015-03-17 10:37 ` Ian Campbell
2015-03-20 18:16 ` Slutz, Donald Christopher
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=1426500048.18247.7.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=murrayie@yahoo.co.uk \
--cc=xen-devel@lists.xensource.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 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.