All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216026] Fails to compile using gcc 12.1 under Ubuntu 22.04
Date: Wed, 25 May 2022 15:59:01 +0000	[thread overview]
Message-ID: <bug-216026-28872-r8UlFuWvQI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216026-28872@https.bugzilla.kernel.org/>

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

Sean Christopherson (seanjc@google.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |seanjc@google.com

--- Comment #3 from Sean Christopherson (seanjc@google.com) ---
Some of the GCC-12 errors, including this one[*], are likely GCC bugs.  The KVM
code has existed for many, many years, i.e. this wasn't something introduced in
v5.18.  I am working on a small series to guard against KVM bugs in this area,
which will in theory squash this warning, but unless someone can prove that an
out-of-bounds access really truly is possible, I doubt any "fix" for this will
be backported to already-released kernels.

Your best bet is to build with CONFIG_WERROR=n and CONFIG_KVM_WERROR=n so that
GCC-12's zealotry doesn't break the build.

[*] https://lore.kernel.org/all/YofQlBrlx18J7h9Y@google.com

-- 
You may reply to this email to add a comment.

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

  parent reply	other threads:[~2022-05-25 15:59 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25  7:56 [Bug 216026] New: Fails to compile using gcc 12.1 under Ubuntu 22.04 bugzilla-daemon
2022-05-25  8:17 ` [Bug 216026] " bugzilla-daemon
2022-05-25  8:34 ` bugzilla-daemon
2022-05-25 15:59 ` bugzilla-daemon [this message]
2022-05-25 19:40 ` bugzilla-daemon
2022-05-25 20:51 ` bugzilla-daemon
2022-05-26  1:48 ` bugzilla-daemon
2022-05-27  0:52 ` bugzilla-daemon
2022-05-30 19:47 ` bugzilla-daemon
2022-05-30 19:57 ` bugzilla-daemon
2022-05-31  2:10 ` bugzilla-daemon
2022-05-31 10:42 ` bugzilla-daemon
2022-06-01  6:56 ` bugzilla-daemon
2022-06-01  7:04 ` bugzilla-daemon
2022-06-07  7:41 ` bugzilla-daemon
2022-06-07  8:54 ` bugzilla-daemon
2022-06-10 22:48 ` bugzilla-daemon
2022-06-13 15:16 ` bugzilla-daemon
2022-06-14 10:56 ` bugzilla-daemon
2022-06-15 14:05 ` bugzilla-daemon
2022-06-15 22:11 ` bugzilla-daemon
2022-06-15 22:17 ` bugzilla-daemon
2022-06-16 21:22 ` bugzilla-daemon
2022-06-16 21:25 ` bugzilla-daemon
2022-06-18 17:34 ` bugzilla-daemon
2022-06-19  0:29 ` bugzilla-daemon
2022-06-19  0:30 ` bugzilla-daemon
2022-06-19  0:31 ` bugzilla-daemon
2022-06-20  4:35 ` bugzilla-daemon
2022-06-20  7:16 ` bugzilla-daemon
2022-06-20 13:39 ` bugzilla-daemon
2022-06-20 14:01 ` bugzilla-daemon
2022-06-20 14:33 ` bugzilla-daemon
2022-06-20 15:25 ` bugzilla-daemon
2022-06-21  5:46 ` bugzilla-daemon
2022-06-21 11:23 ` bugzilla-daemon
2022-06-21 16:05 ` bugzilla-daemon
2022-06-21 16:06 ` bugzilla-daemon
2022-06-21 21:45 ` bugzilla-daemon
2022-06-24  0:00 ` bugzilla-daemon
2022-06-26 19:04 ` bugzilla-daemon
2022-06-27  7:41 ` bugzilla-daemon
2022-06-27 14:21 ` 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-216026-28872-r8UlFuWvQI@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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.