From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH 2/8] builtin: define a symbol_op for a generic op acting on integer
Date: Sun, 11 Apr 2021 21:40:19 +0100 [thread overview]
Message-ID: <9bca36d1-b84a-7b6f-37cb-fd5285a86f0f@ramsayjones.plus.com> (raw)
In-Reply-To: <20210410133045.53189-3-luc.vanoostenryck@gmail.com>
On 10/04/2021 14:30, Luc Van Oostenryck wrote:
> This can be used to define some generic (polymorphic) builtin
> with a signature like:
> op(T)
> op(T, T)
> op(T,T, ... T)
> where T is some integer type.
>
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> ---
> builtin.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
> builtin.h | 2 ++
> 2 files changed, 52 insertions(+)
>
> diff --git a/builtin.c b/builtin.c
> index ff03dbab9a06..f03bf109c818 100644
> --- a/builtin.c
> +++ b/builtin.c
> @@ -390,6 +390,56 @@ static struct symbol_op overflow_p_op = {
> };
>
I must apologize in advance, I've got a head cold, I'm tired and
should probably not be commenting (especially since I am only
skimming these patches), but ...
>
> +///
> +// Evaluate the arguments of 'generic' integer operators.
> +//
> +// All arguments must be the same basic integer type and
> +// their number comes from the prototype and is already checked.
> +static int evaluate_generic_int_op(struct expression *expr)
> +{
> + struct symbol *fntype = expr->fn->ctype->ctype.base_type;
> + struct symbol_list *types = NULL;
> + struct symbol *ctype = NULL;
> + struct expression *arg;
> + struct symbol *t;
> + int n = 0;
> +
> + PREPARE_PTR_LIST(fntype->arguments, t);
So, t is used to iterate over the 'fntype->arguments' (which is to say
the generic type T), ...
> + FOR_EACH_PTR(expr->args, arg) {
> + struct symbol *type;
> +
> + if (++n == 1) {
> + t = arg->ctype;
which is then set to the first argument type, here ...
> + if (!arg || !(type = arg->ctype))
> + return 0;
> + if (type->type == SYM_NODE)
> + type = type->ctype.base_type;
> + if (!type)
> + return 0;
> + if (type->ctype.base_type != &int_type || type == &bool_ctype)
> + goto err;
> + } else {
> + t = ctype;
... and thereafter (for 2, 3, ...) to NULL. (ctype is not set to anything
and it is initialized to NULL above).
> + }
> + add_ptr_list(&types, t);
... so this 'types' list is just {arg->ctype, NULL, NULL, ...}
> + NEXT_PTR_LIST(t);
> + } END_FOR_EACH_PTR(arg);
> + FINISH_PTR_LIST(t);
> + return evaluate_arguments(types, expr->args);
> +
> +err:
> + sparse_error(arg->pos, "non-integer type for argument %d:", n);
here, n will only ever be 1, right? (only way to get here, via goto, from
the n == 1 conditional, above).
> + info(arg->pos, " %s", show_typename(arg->ctype));
> + expr->ctype = &bad_ctype;
> + return 0;
> +}
I stopped reading here. (I probably should have stopped sooner! ;).
ATB,
Ramsay Jones
> +
> +struct symbol_op generic_int_op = {
> + .args = args_prototype,
> + .evaluate = evaluate_generic_int_op,
> +};
> +
> +
> static int eval_atomic_common(struct expression *expr)
> {
> struct symbol *fntype = expr->fn->ctype->ctype.base_type;
> diff --git a/builtin.h b/builtin.h
> index 9cb6728444fe..5fe77c926244 100644
> --- a/builtin.h
> +++ b/builtin.h
> @@ -14,4 +14,6 @@ struct builtin_fn {
>
> void declare_builtins(int stream, const struct builtin_fn tbl[]);
>
> +extern struct symbol_op generic_int_op;
> +
> #endif
>
next prev parent reply other threads:[~2021-04-11 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 13:30 [PATCH 0/8] scheck: add a symbolic checker for sparse Luc Van Oostenryck
2021-04-10 13:30 ` [PATCH 1/8] export declare_builtins() Luc Van Oostenryck
2021-04-10 13:30 ` [PATCH 2/8] builtin: define a symbol_op for a generic op acting on integer Luc Van Oostenryck
2021-04-11 20:40 ` Ramsay Jones [this message]
2021-04-11 22:05 ` Luc Van Oostenryck
2021-04-10 13:30 ` [PATCH 3/8] .gitignore is a bit too greedy Luc Van Oostenryck
2021-04-10 13:30 ` [PATCH 4/8] scheck: add a symbolic checker Luc Van Oostenryck
2021-04-10 13:30 ` [PATCH 5/8] scheck: assert_eq() Luc Van Oostenryck
2021-04-10 13:30 ` [PATCH 6/8] scheck: allow multiple assertions Luc Van Oostenryck
2021-04-10 13:30 ` [PATCH 7/8] scheck: assert_const() Luc Van Oostenryck
2021-04-10 13:30 ` [PATCH 8/8] scheck: support pre-conditions via __assume() 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=9bca36d1-b84a-7b6f-37cb-fd5285a86f0f@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.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).