From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Prepending '*' to an expression (Was: [PATCH V2] scripts/coccinelle/misc/memcpy-assign.cocci: Replace memcpy with struct assignment)
Date: Thu, 24 Jan 2013 19:05:45 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1301241900190.2449@hadrien> (raw)
In-Reply-To: <510173B3.9090002@redhat.com>
On Thu, 24 Jan 2013, Michael Stefaniuc wrote:
> Hello,
>
> On 01/23/2013 11:06 PM, Peter Senna Tschudin wrote:
> > There are error-prone memcpy() that can be replaced by struct
> > assignment that are type-safe and much easier to read. This semantic
> > patch looks for memcpy() that can be replaced by struct assignment.
> thanks for the script by Peter this script as it proved useful for Wine
> too. Though in one case it generated the wrong patch.
>
> @@
> struct struct_name to;
> struct struct_name from;
> @@
>
> 'to' and 'from' above are expressions and not identifiers; that's a
> feature. The bug happened in the replacement
> - memcpy(foos + count, &foo, sizeof(struct foo_t));
> + *foos + count = foo;
>
> Shouldn't cocinelle automatically add the parenthesis when prepending a
> '*' or '&' to an expression which isn't an identifier?
Perhaps it would be possible, but there is nothing in place to do that.
Part of a solution would be to declare the metavariable in the
unparenthesized case as an idexpression, ie idexpression struct
struct_name *to. Then one could have a rule for an arbitrary expression
afterwards, ie with the metavariable declaration above, that would
explicitly add parentheses.
With that though you would end up with parentheses around eg x->y, because
that is not considered to be an identifier. So one would also need a
separate rule in the middle for that case. To ensure that the types are
OK, you should be able to do:
@@
struct struct_name *to;
expression e;
identifier f;
...
@@
e->f at to
This should match the same term against both the pattern e->f and the
pattern to.
Thanks for testing.
julia
next prev parent reply other threads:[~2013-01-24 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 22:06 [Cocci] [PATCH V2] scripts/coccinelle/misc/memcpy-assign.cocci: Replace memcpy with struct assignment Peter Senna Tschudin
2013-01-24 17:47 ` [Cocci] Prepending '*' to an expression (Was: [PATCH V2] scripts/coccinelle/misc/memcpy-assign.cocci: Replace memcpy with struct assignment) Michael Stefaniuc
2013-01-24 18:05 ` Julia Lawall [this message]
2013-01-26 1:28 ` Peter Senna Tschudin
2013-01-27 20:46 ` Michael Stefaniuc
2013-01-28 22:04 ` Julia Lawall
2013-01-29 21:38 ` Michael Stefaniuc
2013-01-29 21:42 ` Julia Lawall
2013-02-06 14:37 ` Michael Stefaniuc
2013-02-22 10:25 ` [Cocci] [PATCH V2] scripts/coccinelle/misc/memcpy-assign.cocci: Replace memcpy with struct assignment Michal Marek
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=alpine.DEB.2.02.1301241900190.2449@hadrien \
--to=julia.lawall@lip6.fr \
--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