On Wed, 27 Jan 2021, James K. Lowden wrote:
> I don't understand how, if it's possible, to qualify a function in a
> rule. I want the class of all functions having a parameter of a
> particular type.
>
> The code I'm working with has hundreds of unnecessary casts. Many
> functions take a void* parameter, but are nonetheless called by casting
> the parameter. For example, the parameters to memcpy(3) often
> have casts applied.
>
> I imagine writing a rule like
>
> @@
> type T, D;
> identifier F(void*);
> identifier D * data;
> @@
>
> - F((T*)data)
> + F(data)
>
> but that doesn't work, and I haven't found anything that does.
>
> In the kmalloc examples, I see things like
>
> - \(kmalloc|kcmalloc\)(...)
> + mumble something
>
> but that forces me to enumerate all such function names. It seems
> vaguely like positions would do the trick, but, well, vaguely.
>
> Is there a way?
In principle, you should be able to specify the type of F. But I'm not at
all sure that that is supported for function names.
Maybe it would suffice to do:
@fn@
identifier F,i;
parameter list[n] ps;
@@
F(ps,void *i,...) { ... }
@@
identifier fn.F;
expression list[fn.n] es;
type T;
expression *e;
@@
F(es,
- (T*)
e, ...)
@ty@
identifier F,i;
parameter list[n] ps;
type t;
@@
t F(ps,void *i,...);
@@
identifier ty.F;
expression list[ty.n] es;
type T;
expression *e;
@@
F(es,
- (T*)
e, ...)
Probably your function prototypes are not in the .c files, but rather in
things that they include. So you would want to use an argument like
--all-includes (include locally mentioned header) or --recursive-includes
(include headers included in other headers). You may want to give some -I
dir arguments to help it find the header files.
julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci