From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Christopher Li <sparse@chrisli.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Potential incorrect simplification
Date: Sun, 6 Aug 2017 18:56:20 +0200 [thread overview]
Message-ID: <CAMHZB6FH7431uaYzuQN4jxhwMSYHLXjrVkUs4xuwsvUsAgkDBQ@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxd30jwczag_GHW3cmqPcBybEi7jfwfku81vW2nHzo_kyA@mail.gmail.com>
On Sun, Aug 6, 2017 at 5:52 PM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
> Hi,
>
> I would like to assert that in the C code there was no attempt to
> access uninitialized value. If you have a look at the original report
> here:
>
> http://marc.info/?l=linux-sparse&m=149070715427276&w=2
>
> You will see that the C code assigns a value to the field before
> attempting to access it as shown below.
>
> s3.onebit = 1;
> if(s3.onebit != 1){
> }
True but this should be solved by patch b1672eab399fdce2c050e8aa07767489a2071981
available since -rc1.
Isn't it the case?
-- Luc
next prev parent reply other threads:[~2017-08-06 16:56 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 12:40 Potential incorrect simplification Dibyendu Majumdar
2017-03-28 13:34 ` Luc Van Oostenryck
2017-03-28 13:58 ` Dibyendu Majumdar
2017-03-28 14:11 ` Luc Van Oostenryck
2017-03-28 14:19 ` Dibyendu Majumdar
2017-03-28 16:20 ` Linus Torvalds
2017-03-28 17:00 ` Luc Van Oostenryck
2017-03-28 18:02 ` Linus Torvalds
2017-03-28 20:27 ` Luc Van Oostenryck
2017-03-28 21:57 ` Linus Torvalds
2017-03-28 22:28 ` Luc Van Oostenryck
2017-03-28 22:22 ` Dibyendu Majumdar
2017-08-06 12:46 ` Christopher Li
2017-08-06 14:00 ` Luc Van Oostenryck
2017-08-06 14:24 ` Christopher Li
2017-08-06 14:54 ` Christopher Li
2017-08-06 15:07 ` Luc Van Oostenryck
2017-08-06 15:51 ` Christopher Li
2017-08-06 16:51 ` Luc Van Oostenryck
2017-08-06 18:35 ` Christopher Li
2017-08-06 19:51 ` Dibyendu Majumdar
2017-08-06 20:08 ` Luc Van Oostenryck
2017-08-06 19:52 ` Luc Van Oostenryck
2017-08-06 23:34 ` Christopher Li
2017-08-07 0:31 ` Luc Van Oostenryck
2017-08-07 0:38 ` Christopher Li
2017-08-06 15:52 ` Dibyendu Majumdar
2017-08-06 16:56 ` Luc Van Oostenryck [this message]
2017-08-06 17:04 ` Dibyendu Majumdar
2017-08-06 17:45 ` Luc Van Oostenryck
2017-08-06 17:58 ` Dibyendu Majumdar
2017-08-06 18:15 ` Luc Van Oostenryck
2017-08-06 18:18 ` Dibyendu Majumdar
2017-08-06 18:31 ` Luc Van Oostenryck
2017-08-07 19:11 ` [PATCH v2 0/8] fix loading of partially defined bitfield Luc Van Oostenryck
2017-08-07 19:11 ` [PATCH v2 1/8] Remove single-store shortcut Luc Van Oostenryck
2017-08-07 21:42 ` Linus Torvalds
2017-08-10 0:29 ` Christopher Li
2017-08-10 0:41 ` Luc Van Oostenryck
2017-08-10 0:53 ` Christopher Li
2017-08-10 11:01 ` Christopher Li
2017-08-10 12:26 ` Luc Van Oostenryck
2017-08-10 13:25 ` Christopher Li
2017-08-07 19:11 ` [PATCH v2 2/8] new helper: def_opcode() Luc Van Oostenryck
2017-08-07 19:12 ` [PATCH v2 3/8] reuse nbr_pseudo_users() Luc Van Oostenryck
2017-08-07 19:12 ` [PATCH v2 4/8] change the masking when loading bitfields Luc Van Oostenryck
2017-08-07 19:12 ` [PATCH v2 5/8] simplify ((A & M') | B ) & M when M' & M == 0 Luc Van Oostenryck
2017-08-07 19:12 ` [PATCH v2 6/8] transform (A & M) >> S to (A >> S) & (M >> S) Luc Van Oostenryck
2017-08-08 0:22 ` Christopher Li
2017-08-08 0:29 ` Luc Van Oostenryck
2017-08-08 1:48 ` Christopher Li
2017-08-08 1:00 ` Linus Torvalds
2017-08-08 1:38 ` Luc Van Oostenryck
2017-08-08 1:50 ` Christopher Li
2017-08-07 19:12 ` [PATCH v2 7/8] transform (A << S) >> S into A & (-1 " Luc Van Oostenryck
2017-08-07 21:54 ` Linus Torvalds
2017-08-07 22:08 ` Luc Van Oostenryck
2017-08-07 22:27 ` Luc Van Oostenryck
2017-08-07 19:12 ` [PATCH v2 8/8] fix: cast of OP_AND only valid if it's an OP_CAST Luc Van Oostenryck
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=CAMHZB6FH7431uaYzuQN4jxhwMSYHLXjrVkUs4xuwsvUsAgkDBQ@mail.gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=mobile@majumdar.org.uk \
--cc=sparse@chrisli.org \
--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;
as well as URLs for NNTP newsgroup(s).