From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] linearize.h: fix some 'selfcheck' warnings
Date: Sun, 28 Feb 2021 22:33:55 +0100 [thread overview]
Message-ID: <20210228213355.ymko6uwbsxj4expj@mail> (raw)
In-Reply-To: <89a7aecb-1a5c-0a43-c9a9-ccee0b12fca6@ramsayjones.plus.com>
On Fri, Feb 26, 2021 at 11:28:43PM +0000, Ramsay Jones wrote:
>
> Commits 34c57a7f ("asm-mem: does it clobber memory?", 2021-02-20) and
> d6721b38 ("asm-mem: does it output to memory?", 2021-02-20) both add
> a single bit bitfield to the 'struct asm' part of the union contained
> within the 'struct instruction'. This causes the 'selfcheck' target
> to issue several 'dubious one-bit signed bitfield' errors.
>
> In order to suppress these errors, change the type of the bitfields to
> an unsigned type.
Thank you,
-- Luc
prev parent reply other threads:[~2021-02-28 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 23:28 [PATCH] linearize.h: fix some 'selfcheck' warnings Ramsay Jones
2021-02-28 21:33 ` Luc Van Oostenryck [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=20210228213355.ymko6uwbsxj4expj@mail \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.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 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).