From: "Christopher Li" <sparse@chrisli.org>
To: Alexey Zaytsev <alexey.zaytsev@gmail.com>
Cc: Tommy Thorn <tommy@numba-tu.com>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Warn about explicit usage of sizeof(void) and sizeof(function)
Date: Thu, 25 Dec 2008 11:45:49 -0800 [thread overview]
Message-ID: <70318cbf0812251145k1fa1e3bbh58b33a1aadf277cc@mail.gmail.com> (raw)
In-Reply-To: <20081225182817.26024.19045.stgit@zaytsev.su>
Hi Alexey,
On Thu, Dec 25, 2008 at 10:36 AM, Alexey Zaytsev
<alexey.zaytsev@gmail.com> wrote:
> I added (hopefully the right way) handling of (sizeof(function)) to the
> patch. function++ was already prohibited.
Can you send me an incremental patch for the sizeof(function) change?
BTW, is it one of the gcc special treatment as well?
Thanks
Chris
On Thu, Dec 25, 2008 at 10:36 AM, Alexey Zaytsev
<alexey.zaytsev@gmail.com> wrote:
> Tommy Thorn wrote:
>> Christopher Li wrote:
>>> 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:
>>>
> I added (hopefully the right way) handling of (sizeof(function)) to the
> patch. function++ was already prohibited.
>>> void *p;
>>>
>>> int i = sizeof(void);
>>> int j = sizeof(*p);
>>>
>
>> I can't test it right now, but does it give a warning for both sizeof's
>> above? If just first results in a warning, then I think that quite
>> reasonable.
>
> Both trigger the warning. I'm not sure this is a problem, as there are
> no such usage cases in the kernel.
>
>
> Running the test on the kernel right now.
>
> --
>
>
> From: Christopher Li <sparse@chrisli.org>
>
> sizeof(void) and sizeof(function) 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>
> [sizeof(function) added by Alexey Zaytsev]
> Signed-off-by: Alexey Zaytsev <alexey.zaytsev@gmail.com>
> ---
> evaluate.c | 13 ++++++++++++-
> symbol.c | 2 +-
> 2 files changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/evaluate.c b/evaluate.c
> index f976645..e82be53 100644
> --- a/evaluate.c
> +++ b/evaluate.c
> @@ -579,7 +579,7 @@ static struct symbol *evaluate_ptr_add(struct expression *expr, struct symbol *i
> }
>
> /* 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;
> @@ -2044,8 +2044,19 @@ static struct symbol *evaluate_sizeof(struct expression *expr)
> 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 (is_function(type->ctype.base_type)) {
> + warning(expr->pos, "expression using sizeof on a function");
> + 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;
> diff --git a/symbol.c b/symbol.c
> index 02844cf..4da253b 100644
> --- a/symbol.c
> +++ b/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 prev parent reply other threads:[~2008-12-25 19:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 2:09 [PATCH] Warn about explicit usage of sizeof(void) Christopher Li
2008-12-25 17:23 ` 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 [this message]
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=70318cbf0812251145k1fa1e3bbh58b33a1aadf277cc@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=alexey.zaytsev@gmail.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).