All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 207173] kvm compiling problem 5.6.x kvm_main.c:2236:42: error: ‘nr_pages_avail’ may be used uninitialized in this function
Date: Tue, 12 May 2020 10:30:30 +0000	[thread overview]
Message-ID: <bug-207173-28872-0nwj29fBoA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207173-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=207173

--- Comment #11 from Mike Auty (mike.auty@gmail.com) ---
I'm also experiencing this, but not on clang, on gcc-10.1.0.  The initially
proposed resolution:

gfn_t nr_pages_avail = 0; 

succeeded.  The alternative resolution:

gfn uninitialized_var(nr_pages_avail);

Needed to be changed to 

gfn_t uninitialized_var(nr_pages_avail);

but also allowed compilation.

The suggestion to mark __gfn_to_hva_many and gfn_to_hva_many as always inline
failed to resolve the problem though.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-05-12 10:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 14:25 [Bug 207173] New: kvm compiling problem 5.6.x kvm_main.c:2236:42: error: ‘nr_pages_avail’ may be used uninitialized in this function bugzilla-daemon
2020-04-12  7:28 ` [Bug 207173] " bugzilla-daemon
2020-04-13 23:41 ` bugzilla-daemon
2020-04-14  9:19 ` bugzilla-daemon
2020-04-14 15:37 ` bugzilla-daemon
2020-04-14 18:53 ` bugzilla-daemon
2020-04-15  1:19 ` bugzilla-daemon
2020-04-15  5:43 ` bugzilla-daemon
2020-04-26  2:10 ` bugzilla-daemon
2020-04-27 16:45 ` bugzilla-daemon
2020-05-10  2:04 ` bugzilla-daemon
2020-05-12 10:30 ` bugzilla-daemon [this message]
2020-05-12 14:37 ` bugzilla-daemon

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=bug-207173-28872-0nwj29fBoA@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.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 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.