From: Bill Wendling <morbo@google.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Jim Mattson <jmattson@google.com>, kvm list <kvm@vger.kernel.org>
Subject: Re: [kvm-unit-tests PATCH] x86: setjmp: ignore clang's "-Wsomtimes-uninitialized" flag
Date: Tue, 10 Sep 2019 21:32:51 -0500 [thread overview]
Message-ID: <CAGG=3QUdb6PsB-pDEvCCEkapnZn0kop-=S1orRrCy5s-BcDm2A@mail.gmail.com> (raw)
In-Reply-To: <CAGG=3QVzO_Cu-TqyddbXZ5CrtPkqxsUHUVdCPHwFTm1BfLgQ0g@mail.gmail.com>
I sent out a separate patch. PTAL. :-)
On Tue, Sep 10, 2019 at 8:42 PM Bill Wendling <morbo@google.com> wrote:
>
> On Tue, Sep 10, 2019 at 12:59 PM Sean Christopherson
> <sean.j.christopherson@intel.com> wrote:
> >
> > On Tue, Sep 10, 2019 at 09:46:36AM -0700, Jim Mattson wrote:
> > > On Mon, Sep 9, 2019 at 2:10 PM Bill Wendling <morbo@google.com> wrote:
> > > >
> > > > Clang complains that "i" might be uninitialized in the "printf"
> > > > statement. This is a false negative, because it's set in the "if"
> > > > statement and then incremented in the loop created by the "longjmp".
> > > >
> > > > Signed-off-by: Bill Wendling <morbo@google.com>
> > > > ---
> > > > x86/setjmp.c | 4 ++++
> > > > 1 file changed, 4 insertions(+)
> > > >
> > > > diff --git a/x86/setjmp.c b/x86/setjmp.c
> > > > index 976a632..cf9adcb 100644
> > > > --- a/x86/setjmp.c
> > > > +++ b/x86/setjmp.c
> > > > @@ -1,6 +1,10 @@
> > > > #include "libcflat.h"
> > > > #include "setjmp.h"
> > > >
> > > > +#ifdef __clang__
> > > > +#pragma clang diagnostic ignored "-Wsometimes-uninitialized"
> > > > +#endif
> > > > +
> > > > int main(void)
> > > > {
> > > > volatile int i;
> > >
> > > Can we just add an initializer here instead?
> >
> > Doing so would also be a good opportunity to actually report on the
> > expected vs. actual value of 'i' instead of printing numbers that are
> > meaningless without diving into the code.
>
> My initial thought about adding an initializer was that the original
> test wanted to ensure that "i" was initialized after the "setjmp"
> call. But if we report the expected/actual value instead it wouldn't
> be an issue as we can set it to something not expected, etc... I'll
> create a patch.
>
> -bw
prev parent reply other threads:[~2019-09-11 2:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 21:09 [kvm-unit-tests PATCH] x86: setjmp: ignore clang's "-Wsomtimes-uninitialized" flag Bill Wendling
2019-09-10 16:46 ` Jim Mattson
2019-09-10 17:59 ` Sean Christopherson
2019-09-11 1:42 ` Bill Wendling
2019-09-11 2:32 ` Bill Wendling [this message]
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='CAGG=3QUdb6PsB-pDEvCCEkapnZn0kop-=S1orRrCy5s-BcDm2A@mail.gmail.com' \
--to=morbo@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=sean.j.christopherson@intel.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.