kvm.vger.kernel.org archive mirror
 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: Wed, 15 Apr 2020 01:19:32 +0000	[thread overview]
Message-ID: <bug-207173-28872-woP3VumN91@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 #6 from Sean Christopherson (sean.j.christopherson@intel.com) ---
Ah, fun.  So this falls into the "not technically a kernel problem" category. 
O3 isn't supported outside of the ARC architecture (no clue why it "needs" O3),
and AFAICT, has never been a selectable Kconfig option outside of ARC.

The false positives with -Wmaybe-uninitialized and -O3 (and -Os) is a known
issue, e.g. the kernel adds -Wno-maybe-uninitialized when compiling with either
of those options.  Unfortunately, there is no direct way to force
CONFIG_CC_DISABLE_WARN_MAYBE_UNINITIALIZED=y.  You could select
CONFIG_CC_OPTIMIZE_FOR_SIZE and then edit your Makefile, but I think that might
have unwanted side effects.

The easiest way to workaround this issue is to do CONFIG_KVM_WERROR=n.  The
false positive warning will still occur, but it won't get escalated to an error
and break your build.  I'm guessing there's a way to get
-Wno-maybe-uninitialized, but disabling -Werror for KVM is easy and doesn't
really have downsides.

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

  parent reply	other threads:[~2020-04-15  1:19 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 [this message]
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
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-woP3VumN91@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).