From: torvic9@mailbox.org
To: Paolo Bonzini <pbonzini@redhat.com>,
"seanjc@google.com" <seanjc@google.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"ndesaulniers@google.com" <ndesaulniers@google.com>,
"nathan@kernel.org" <nathan@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"bp@alien8.de" <bp@alien8.de>
Subject: Re: [BUG] [5.15] Compilation error in arch/x86/kvm/mmu/spte.h with clang-14
Date: Mon, 4 Oct 2021 11:30:38 +0200 (CEST) [thread overview]
Message-ID: <936688112.157288.1633339838738@office.mailbox.org> (raw)
In-Reply-To: <b6abc5a3-39ea-b463-9df5-f50bdcb16d08@redhat.com>
> Paolo Bonzini <pbonzini@redhat.com> hat am 04.10.2021 11:26 geschrieben:
>
>
> On 04/10/21 11:08, torvic9@mailbox.org wrote:
> > I encounter the following issue when compiling 5.15-rc4 with clang-14:
> >
> > In file included from arch/x86/kvm/mmu/mmu.c:27:
> > arch/x86/kvm/mmu/spte.h:318:9: error: use of bitwise '|' with boolean operands [-Werror,-Wbitwise-instead-of-logical]
> > return __is_bad_mt_xwr(rsvd_check, spte) |
> > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > ||
> > arch/x86/kvm/mmu/spte.h:318:9: note: cast one or both operands to int to silence this warning
>
> The warning is wrong, as mentioned in the line right above:
So it's an issue with clang-14 then?
(I add Nick and Nathan)
>
> /*
> * Use a bitwise-OR instead of a logical-OR to aggregate the reserved
> * bits and EPT's invalid memtype/XWR checks to avoid an extra Jcc
> * (this is extremely unlikely to be short-circuited as true).
> */
>
> Paolo
next prev parent reply other threads:[~2021-10-04 9:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 9:08 [BUG] [5.15] Compilation error in arch/x86/kvm/mmu/spte.h with clang-14 torvic9
2021-10-04 9:26 ` Paolo Bonzini
2021-10-04 9:30 ` torvic9 [this message]
2021-10-04 9:49 ` Paolo Bonzini
2021-10-04 10:10 ` torvic9
2021-10-04 14:33 ` torvic9
2021-10-04 16:13 ` Nick Desaulniers
2021-10-04 17:12 ` Jim Mattson
2021-10-14 17:50 ` Nathan Chancellor
2021-10-14 18:31 ` Sean Christopherson
2021-10-14 19:06 ` Nick Desaulniers
2021-10-14 20:50 ` Paolo Bonzini
2021-10-15 9:17 ` Christophe de Dinechin
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=936688112.157288.1633339838738@office.mailbox.org \
--to=torvic9@mailbox.org \
--cc=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@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 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.