From: Nathan Chancellor <nathan@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [GIT PULL] KVM fixes for Linux 6.11-rc7
Date: Fri, 6 Sep 2024 16:39:58 -0700 [thread overview]
Message-ID: <20240906233958.GA1968981@thelio-3990X> (raw)
In-Reply-To: <CAHk-=wjK7HF3dQT8q_6fr3eLGvKS+c46PdYNVAsHRyQRgcgiyw@mail.gmail.com>
On Fri, Sep 06, 2024 at 03:38:16PM -0700, Linus Torvalds wrote:
> On Fri, 6 Sept 2024 at 08:45, Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> > - Specialize return value of KVM_CHECK_EXTENSION(KVM_CAP_READONLY_MEM),
> > based on VM type
>
> Grr. This actually causes a build warning with clang, but I didn't
> notice in my "between pulls" build check, because that is with gcc.
>
> So now it's merged with this error:
>
> arch/x86/kvm/x86.c:4819:2: error: unannotated fall-through between
> switch labels [-Werror,-Wimplicit-fallthrough]
>
> and I'm actually surprised that gcc didn't warn about this too.
Yeah, GCC does not warn when falling through to a break or return, as I
mention in the patch I sent for this (I was going to keep an eye out for
the pull request and comment before it went in but looks like I missed
it):
https://lore.kernel.org/kvm/20240905-kvm-x86-avoid-clang-implicit-fallthrough-v1-1-f2e785f1aa45@kernel.org/
> We definitely enable -Wimplicit-fallthrough on gcc too, but apparently
> it's not functional: falling through to a "break" statement seems to
> not warn with gcc. Which is nonsensical, but whatever.
This was brought up to GCC at one point and they considered its current
behavior as working as intended from my understanding:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91432
Cheers,
Nathan
next prev parent reply other threads:[~2024-09-06 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 15:45 Paolo Bonzini
2024-09-06 20:28 ` pr-tracker-bot
2024-09-06 22:38 ` Linus Torvalds
2024-09-06 23:39 ` Nathan Chancellor [this message]
2024-09-07 0:48 ` Linus Torvalds
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=20240906233958.GA1968981@thelio-3990X \
--to=nathan@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®