From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Dibyendu Majumdar <mobile@majumdar.org.uk>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH 0/3] fix loading of partially defined bitfield
Date: Sun, 6 Aug 2017 22:00:43 -0400 [thread overview]
Message-ID: <CANeU7Qmkhs9wZNMjkxamML0XZD=WaVX3RTWy_RDXMYZQPy-csw@mail.gmail.com> (raw)
In-Reply-To: <CANeU7Q=3k4yqMuzgjQPh+Hx_Erjggzv4=_92GMXCUbLW4uwvfg@mail.gmail.com>
On Sun, Aug 6, 2017 at 9:59 PM, Christopher Li <sparse@chrisli.org> wrote:
> On Sun, Aug 6, 2017 at 9:33 PM, Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
>> The goal of this series is to fix the problem present in sparse
>> when a bitfield in an uninitialized automatic variable is first
>> set then read-back.
>>
>> In this case the bitfield itself is initialized but not the
>> remaining of the structure/word and sparse was not smart
>> enough to handle it.
>>
>> This is for testing only and the patches are not meant to
>> be applied on the main tree becasue it need the new SSA
>> construction to handle the undefined vars correctly.
>>
>> (two other simplifications is also needed to make the
>> generated code a no-op as it should be but not yet
>> implemented).
>>
>> The whole code is available in the git repository at:
>>
>> git://github.com/lucvoo/sparse.git fix-loading-partialy-defined-bitfields
>
> Is this for RC5?
Sorry I did not read your description very well.
You said it is not for main line yet.
Chris
prev parent reply other threads:[~2017-08-07 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 1:33 [PATCH 0/3] fix loading of partially defined bitfield Luc Van Oostenryck
2017-08-07 1:33 ` [PATCH 1/3] new helper: def_opcode() Luc Van Oostenryck
2017-08-07 1:33 ` [PATCH 2/3] change loading of bitfields Luc Van Oostenryck
2017-08-07 1:33 ` [PATCH 3/3] simplify ((A & M') | B ) & M when M' & M == 0 Luc Van Oostenryck
2017-08-07 1:59 ` [PATCH 0/3] fix loading of partially defined bitfield Christopher Li
2017-08-07 2:00 ` Christopher Li [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='CANeU7Qmkhs9wZNMjkxamML0XZD=WaVX3RTWy_RDXMYZQPy-csw@mail.gmail.com' \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=mobile@majumdar.org.uk \
/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).