From: Franz Schrober <franzschrober@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: jw+debian@jameswestby.net, sparse@chrisli.org,
franzschrober@gmail.com, Franz Schrober <franzschrober@yahoo.de>
Subject: [PATCHv2 5/5] sparse: Also check bit_offset when checking implicit casts
Date: Thu, 28 Nov 2013 11:16:22 +0100 [thread overview]
Message-ID: <1385633782-775-6-git-send-email-franzschrober@gmail.com> (raw)
In-Reply-To: <1385633782-775-1-git-send-email-franzschrober@gmail.com>
From: Franz Schrober <franzschrober@yahoo.de>
The comparison in same_cast_type only checked the bit_size of the new and the
old symbol. The bit_offset was only compared with itself and thus would always
be true. Instead Linus most likely wanted to compare the bit_offset of the new
and the old symbol. This regression was introduced in
47f53396a1d62719c44941f84370ead80181728e ("If two implied casts end up undoing
each other, just remove them.").
Reported-by: James Westby <jw+debian@jameswestby.net>
Signed-off-by: Franz Schrober <franzschrober@yahoo.de>
---
evaluate.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/evaluate.c b/evaluate.c
index 5b643d8..6655615 100644
--- a/evaluate.c
+++ b/evaluate.c
@@ -191,7 +191,8 @@ left:
static int same_cast_type(struct symbol *orig, struct symbol *new)
{
- return orig->bit_size == new->bit_size && orig->bit_offset == orig->bit_offset;
+ return orig->bit_size == new->bit_size &&
+ orig->bit_offset == new->bit_offset;
}
static struct symbol *base_type(struct symbol *node, unsigned long *modp, unsigned long *asp)
--
1.8.4.4
next prev parent reply other threads:[~2013-11-28 10:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 10:16 [PATCHv2 0/5] sparse: Relicense from non-dfsg-free OSL 1.1 to MIT license Franz Schrober
2013-11-28 10:16 ` [PATCHv2 1/5] Revert "Update the information in README about using the library." Franz Schrober
2013-11-28 10:16 ` [PATCHv2 2/5] Revert "Fix mistaken comparison that becomes a no-op." Franz Schrober
2013-11-28 10:16 ` [PATCHv2 3/5] sparse: Relicense under the MIT license Franz Schrober
2013-11-28 10:16 ` [PATCHv2 4/5] FAQ: Remove outdated section about the license Franz Schrober
2013-11-28 21:05 ` Josh Triplett
2013-11-29 12:19 ` Schrober
2013-11-29 12:30 ` [PATCHv3 4/5] FAQ: Remove outdated sections " Franz Schrober
2013-11-28 10:16 ` Franz Schrober [this message]
2013-11-28 10:22 ` [PATCHv2 0/5] sparse: Relicense from non-dfsg-free OSL 1.1 to MIT license Franz Schrober
[not found] ` <CANeU7Qkjvh4OeCWANFbV6COU4NvjB1pUGXwry7CNCrQz8WG0zw@mail.gmail.com>
2013-11-29 23:18 ` Fwd: " Christopher Li
2013-11-30 12:48 ` Franz Schrober
2013-12-03 8:17 ` Franz Schrober
2013-12-03 10:37 ` Dan Carpenter
2013-12-03 11:02 ` Schrober
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=1385633782-775-6-git-send-email-franzschrober@gmail.com \
--to=franzschrober@gmail.com \
--cc=franzschrober@yahoo.de \
--cc=jw+debian@jameswestby.net \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).