From: "Christopher Li" <sparse@chrisli.org>
To: Tommy Thorn <tommy@numba-tu.com>
Cc: David Given <dg@cowlark.com>, linux-sparse@vger.kernel.org
Subject: [PATCH] Warn about explicit usage of sizeof(void)
Date: Wed, 24 Dec 2008 18:09:14 -0800 [thread overview]
Message-ID: <70318cbf0812241809h158e8767k30dce82acd886ffa@mail.gmail.com> (raw)
On Wed, Dec 24, 2008 at 4:15 PM, Christopher Li <sparse@chrisli.org> wrote:
> On Wed, Dec 24, 2008 at 3:35 PM, Tommy Thorn <tommy@numba-tu.com> wrote:
>>
>> You can't have one without the other as you will break identities like
>>
>> (uintptr_t) (x + k) === (uintptr_t) x + sizeof (typeof (x)) * k
>>
>> which could appear in a macro.
>
> Right. That is exactly the place I actuall want to know. We should
> consider fix that in the source to have proper type. I expect there is
> not much place in the kernel use that.
I think you do have a point that from the "spase as a compiler" point
of view, there is need to maintain the compatibility with gcc. And I do
care about the current patch breaking the assumption of using
void_ctype.bit_size.
So here is what I got. A patch address both of our need. It gives warning
of using sizeof(void) explicitly. void* + offset will continue to work without
warnings. It will also make is_byte_type() continue to work as it was
before.
Here is my test script:
void *p;
int i = sizeof(void);
int j = sizeof(*p);
void* foo(void)
{
return p + 1;
}
I run the kernel compile with C=2, guess what. None of the current
kernel code use sizeof(void) explicitly. So that is good news.
Every one happy?
Chris
============================================================
Warn about explicit usage of sizeof(void)
sizeof(void) still evaluate as 1 after the warning.
void_ctype.bit_size remain zero so is_byte_type()
will continue to work.
Signed-Off-By: Christopher Li <sparse@chrisli.org>
Index: sparse.chrisl/evaluate.c
===================================================================
--- sparse.chrisl.orig/evaluate.c
+++ sparse.chrisl/evaluate.c
@@ -584,7 +584,7 @@ static struct symbol *evaluate_ptr_add(s
}
/* Get the size of whatever the pointer points to */
- multiply = bits_to_bytes(base->bit_size);
+ multiply = (base == &void_ctype) ? 1 : bits_to_bytes(base->bit_size);
if (ctype == &null_ctype)
ctype = &ptr_ctype;
@@ -2049,8 +2049,14 @@ static struct symbol *evaluate_sizeof(st
return NULL;
size = type->bit_size;
+
+ if (type->ctype.base_type == &void_ctype) {
+ warning(expr->pos, "expression using sizeof(void)");
+ size = bits_in_char;
+ }
if ((size < 0) || (size & (bits_in_char - 1)))
expression_error(expr, "cannot size expression");
+
expr->type = EXPR_VALUE;
expr->value = bits_to_bytes(size);
expr->taint = 0;
Index: sparse.chrisl/symbol.c
===================================================================
--- sparse.chrisl.orig/symbol.c
+++ sparse.chrisl/symbol.c
@@ -834,7 +834,7 @@ static const struct ctype_declare {
struct symbol *base_type;
} ctype_declaration[] = {
{ &bool_ctype, SYM_BASETYPE, MOD_UNSIGNED, &bits_in_bool,
&max_int_alignment, &int_type },
- { &void_ctype, SYM_BASETYPE, 0, &bits_in_char, NULL, NULL },
+ { &void_ctype, SYM_BASETYPE, 0, NULL, NULL, NULL },
{ &type_ctype, SYM_BASETYPE, MOD_TYPE, NULL, NULL, NULL },
{ &incomplete_ctype,SYM_BASETYPE, 0, NULL, NULL, NULL },
{ &bad_ctype, SYM_BASETYPE, 0, NULL, NULL, NULL },
next reply other threads:[~2008-12-25 2:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 2:09 Christopher Li [this message]
2008-12-25 17:23 ` [PATCH] Warn about explicit usage of sizeof(void) Tommy Thorn
2008-12-25 18:36 ` [PATCH] Warn about explicit usage of sizeof(void) and sizeof(function) Alexey Zaytsev
2008-12-25 19:45 ` Christopher Li
2008-12-25 20:10 ` [PATCH] Also warn about sizeof(function) Alexey Zaytsev
2008-12-26 0:48 ` Christopher Li
2008-12-28 15:14 ` [PATCH] Null ctype should have ptr_ctype as its base type Alexey Zaytsev
2008-12-28 20:52 ` Christopher Li
2008-12-28 21:38 ` Alexey Zaytsev
2008-12-29 7:32 ` Christopher Li
2008-12-29 9:03 ` Alexey Zaytsev
2008-12-25 18:48 ` [PATCH] Warn about explicit usage of sizeof(void) Christopher Li
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=70318cbf0812241809h158e8767k30dce82acd886ffa@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=dg@cowlark.com \
--cc=linux-sparse@vger.kernel.org \
--cc=tommy@numba-tu.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).