From: Luca Coelho <luca@coelho.fi>
To: cocci@inria.fr
Cc: julia.lawall@inria.fr
Subject: [cocci] Nested macros
Date: Fri, 27 Jan 2023 19:07:51 +0200 [thread overview]
Message-ID: <df710cc39e1da39521f09827f5528703887e9bce.camel@coelho.fi> (raw)
Hi,
I've been struggling with a change I want to make, so I hope someone
can help.
Basically I have something like this in the code:
/* regs below are bits 15:0 */
#define _MIPIA_HSYNC_PADDING_COUNT (_MIPI_MMIO_BASE(dev_priv) + 0xb028)
#define _MIPIC_HSYNC_PADDING_COUNT (_MIPI_MMIO_BASE(dev_priv) + 0xb828)
#define MIPI_HSYNC_PADDING_COUNT(port) _MMIO_MIPI(port, _MIPIA_HSYNC_PADDING_COUNT, _MIPIC_HSYNC_PADDING_COUNT)
As you can see, these macros assume that the calling functions have a
local called dev_priv, and I want to fix that.
So, I'm trying to find all users of macros that have this construct.
My problem is matching the nesting in the macros.
I have tried this:
@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;
@@
-nm
+foo
(this last rule is just for testing if anything is matching, obviously)
But the "nested_macros" rule doesn't seem to work. Does anyone know
how I can solve this?
Thanks!
--
Cheers,
Luca.
next reply other threads:[~2023-01-27 17:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 17:07 Luca Coelho [this message]
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
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=df710cc39e1da39521f09827f5528703887e9bce.camel@coelho.fi \
--to=luca@coelho.fi \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).