All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Markus Elfring <Markus.Elfring@web.de>,
	Julia Lawall <julia.lawall@inria.fr>
Cc: cocci@inria.fr
Subject: Re: [cocci] Adding a parameter for special macro calls with SmPL
Date: Sun, 29 Jan 2023 21:11:20 +0200	[thread overview]
Message-ID: <e111e4c0ef6fc93576d41a625045ca282ab41bfb.camel@coelho.fi> (raw)
In-Reply-To: <0913ebfd-6ec2-722a-fc17-e609ce0b8770@web.de>

On Sun, 2023-01-29 at 19:01 +0100, Markus Elfring wrote:
> > @macros_noargs@
> > identifier m;
> > expression e =~ "dev_priv";
> > @@
> > #define m <+...e...+>
> > 
> > @nested_macros@
> > identifier macros_noargs.m;
> > identifier nm;
> > identifier list il;
> > @@
> > #define nm(il) <+...m...+>
> > 
> > @@
> > identifier nested_macros.nm;
> > identifier list il;
> > expression e;
> > @@
> > -#define nm(il) e
> > +#define nm(dev_priv, il) e
> > 
> > @@
> > identifier nested_macros.nm;
> > identifier dev_priv, f;
> > expression e;
> > expression list il;
> > @@
> > f(...) {
> > 	...
> > (
> > 	struct drm_i915_private *dev_priv = e;
> > > 
> > 	struct drm_i915_private *dev_priv;
> > )
> 
> 
> I suggest to another look at the isomorphism “decl_init”.
> https://gitlab.inria.fr/coccinelle/coccinelle/-
> /blob/b9603af4eca7f4c771d57a3861855332e9bb1c4c/standard.iso#L465

Thanks, I took a look, the optional initialization is better, indeed.

> 
> 
> 
> > 	<+...
> > -	nm(il)
> > +	nm(dev_priv, il)
> > 	...+>
> > }
> > 
> > 
> > The idea is that all the macros that are implicitly using dev_priv,
> > will have a new argument where dev_priv is passed.
> 
> 
> Your description evolved for the desired transformation considerably.

Yes, sorry, I wanted to keep it as simple as possible, but leaving most
of the story out was indeed a problem, because it was lacking context.


> How do you think about to use the following SmPL script variant?
> 
> 
> @macros_noargs@
> identifier m;
> expression e =~ "dev_priv";
> @@
> #define m <+...e...+>
> 
> @nested_macros@
> identifier macros_noargs.m, nm;
> identifier list il;
> @@
> #define nm(il) <+...m...+>
> 
> @addition1@
> identifier nested_macros.nm;
> identifier list il;
> expression e;
> @@
> -#define nm(il) e
> +#define nm(dev_priv, il) e
> 
> @addition2@
> identifier nested_macros.nm, dev_priv, f;
> expression list el;
> @@
>  f(...)
>  {
>  ...
>  struct drm_i915_private *dev_priv;
>  <+...
>  nm(
> +   dev_priv,
>     el)
>  ...+>
>  }

This is nice, I'll change it.


> > After mangling a lot with the rules, I can see that this now works,
> 
> 
> This understanding is nice.
> 
> 
> 
> > but only if I select the vlv_dsi.c file alone, like this:
> 
> 
> This observation will probably need further explanations.
> 
> 
> 
> > Of course, I can work around this by using find and running spatch
> > individually in every file... But not ideal.
> 
> 
> The Coccinelle software should take care of corresponding source file
> searches already.

It should, but it doesn't seem to be working properly.

--
Cheers,
Luca.

  reply	other threads:[~2023-01-29 20:10 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 17:07 [cocci] Nested macros Luca Coelho
2023-01-27 18:34 ` [cocci] Checking selected macro calls with SmPL Markus Elfring
2023-01-27 20:52 ` [cocci] Nested macros Julia Lawall
2023-01-27 22:00   ` Luca Coelho
2023-01-28  9:19     ` Julia Lawall
2023-01-28  9:25       ` Luca Coelho
2023-01-28  9:46     ` [cocci] Searching for special function implementations with SmPL Markus Elfring
2023-01-28  9:49       ` Julia Lawall
2023-01-28 10:03         ` Luca Coelho
2023-01-28 13:33           ` Julia Lawall
2023-01-29 16:39             ` Luca Coelho
2023-01-29 17:28               ` Julia Lawall
2023-01-29 17:55                 ` Luca Coelho
2023-01-29 19:15                   ` Luca Coelho
2023-01-29 20:09                     ` Julia Lawall
2023-01-30  6:32                       ` Luca Coelho
2023-01-30  8:37                         ` Julia Lawall
2023-01-30  8:50                           ` Luca Coelho
2023-01-30  8:56                             ` Julia Lawall
2023-01-30  9:05                               ` Luca Coelho
2023-01-30  9:34                             ` Markus Elfring
2023-01-30  9:41                               ` Luca Coelho
2023-01-30  9:50                                 ` Markus Elfring
2023-01-30  9:52                                   ` Luca Coelho
2023-01-30  9:55                                     ` Julia Lawall
2023-01-30 10:07                                     ` Markus Elfring
2023-01-30 10:47                                     ` Julia Lawall
2023-01-30 10:59                                       ` Luca Coelho
2023-01-30 11:25                                         ` Markus Elfring
2023-01-31 15:57                                         ` Luca Coelho
2023-01-31 15:59                                           ` Luca Coelho
2023-01-31 16:08                                           ` Julia Lawall
2023-01-31 16:10                                             ` Luca Coelho
2023-01-31 16:20                                               ` Julia Lawall
2023-01-29 18:01               ` [cocci] Adding a parameter for special macro calls " Markus Elfring
2023-01-29 19:11                 ` Luca Coelho [this message]
2023-01-28 13:43           ` [cocci] Searching for special function implementations " Markus Elfring
2023-01-29 16:41             ` Luca Coelho

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=e111e4c0ef6fc93576d41a625045ca282ab41bfb.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=Markus.Elfring@web.de \
    --cc=cocci@inria.fr \
    --cc=julia.lawall@inria.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.