From: "James K. Lowden" <jklowden@schemamania.org>
To: cocci@systeme.lip6.fr
Subject: [Cocci] qualified function rule
Date: Wed, 27 Jan 2021 15:23:25 -0500 [thread overview]
Message-ID: <20210127152325.5692b2e6eb7b8ed82d91262b@schemamania.org> (raw)
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?
--jkl
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next reply other threads:[~2021-01-27 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 20:23 James K. Lowden [this message]
2021-01-27 20:35 ` [Cocci] qualified function rule Julia Lawall
2021-01-30 3:53 ` Mansour Moufid
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=20210127152325.5692b2e6eb7b8ed82d91262b@schemamania.org \
--to=jklowden@schemamania.org \
--cc=cocci@systeme.lip6.fr \
/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).