All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Julia Lawall <julia.lawall@inria.fr>,
	Markus Elfring <Markus.Elfring@web.de>
Cc: cocci@inria.fr
Subject: Re: [cocci] Searching for special function implementations with SmPL
Date: Sat, 28 Jan 2023 12:03:44 +0200	[thread overview]
Message-ID: <8f3f48170bab688aff69571913dbe27fc195fe1f.camel@coelho.fi> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2301281048270.2822@hadrien>

On Sat, 2023-01-28 at 10:49 +0100, Julia Lawall wrote:
> 
> On Sat, 28 Jan 2023, Markus Elfring wrote:
> 
> > > @@
> > > identifier nested_macros.nm;
> > > function f;
> > > identifier dev_priv;
> > 
> > 
> > How do you think about to use the following SmPL code variant instead of
> > the metavariable type “function”?
> > 
> > 
> > identifier dev_priv, f;
> 
> Good suggestion,  Function is not really supported.  I think it behaves
> just like identifier, but it would be better to just use identifier.
> Function was an idea thta never actually got implemented.

Good idea, I generally don't use function, but I'd been trying lots of
different things before I reached out for help. 🙂 I guess I tried with
function at some point and then ended up leaving it there.

Now I tried with f as identifier, but it didn't make a difference.

I can actually match _one_ of the occurrences now, but there are many
other ones that are not matching...

This is what I'm using:

@macros_noargs@
identifier m;
expression e =~ "dev_priv";
@@
#define m <+...e...+>

@nested_macros@
identifier macros_noargs.m;
identifier nm;
@@
#define nm(...) <+...m...+>

@@
identifier nested_macros.nm;
identifier dev_priv, f;
expression e;
@@
f(...) {
	...
-	struct drm_i915_private *dev_priv = e;
+	struct drm_i915_private *i915 = e;

	<+...
	nm(...)
	...+>
}

...and this is the command line:

spatch --sp-file ~/dev_priv_i915.spatch -I drivers/gpu/drm/i915/display \
 --recursive-includes --in-place --dir ./drivers/gpu/drm/i915/display

...and this is the only match I get:

HANDLING: ./drivers/gpu/drm/i915/display/intel_display.c
diff = 
diff -u -p a/intel_display.c b/intel_display.c
--- a/intel_display.c
+++ b/intel_display.c
@@ -3943,7 +3943,7 @@ static bool bxt_get_dsi_transcoder_state
 					 struct intel_display_power_domain_set *power_domain_set)
 {
 	struct drm_device *dev = crtc->base.dev;
-	struct drm_i915_private *dev_priv = to_i915(dev);
+	struct drm_i915_private *i915 = to_i915(dev);
 	enum transcoder cpu_transcoder;
 	enum port port;
 	u32 tmp;

Many other files are handled, but there are no matches, though I
believe there should be.

--
Cheers,
Luca.

  reply	other threads:[~2023-01-28 10:42 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 [this message]
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
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=8f3f48170bab688aff69571913dbe27fc195fe1f.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.