From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Match #define in cocci
Date: Thu, 15 Sep 2016 08:03:56 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1609150803290.6497@hadrien> (raw)
In-Reply-To: <CAHKzcEMih-YHeaaa6hp1-Hf3PUY7GDdqG90wL6zZwuMjaQv=-g@mail.gmail.com>
On Thu, 15 Sep 2016, Waldemar Rymarkiewicz wrote:
> >
> > Could you send the exact semantic patch that you tried? Coccinelle should
> > allos parsing #defines.
>
> Simply
>
> @@
> @@
> -#define pr_fmt(fmt) KBUILD_MODNAME
>
> works, but
>
> @@
> @@
> -#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
>
> fails with
>
> Fatal error: exception Failure("minus: parse error: \n = File
> \"patches/1021-pr_fmt_undef.cocci\", line 4, column 38, charpos =
> 59\n around = '\"', whole content = #define pr_fmt(fmt)
> KBUILD_MODNAME \": \" fmt\n")
>
> but even if I want to match just
>
> @@
> @@
> -#define pr_fmt(fmt) KBUILD_MODNAME fmt
>
> it also fails with
>
> Fatal error: exception Failure("minus: parse error: \n = File
> \"patches/1021-pr_fmt_undef.cocci\", line 4, column 0, charpos = 21\n
> around = '#define pr_fmt(', whole content = #define pr_fmt(fmt)
> KBUILD_MODNAME fmt\n")
OK, thanks I will look into it. At least in the last case, that is not
the intended behavior.
julia
next prev parent reply other threads:[~2016-09-15 6:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 13:31 [Cocci] Match #define in cocci Waldemar Rymarkiewicz
2016-09-14 14:16 ` Julia Lawall
2016-09-15 5:57 ` Waldemar Rymarkiewicz
2016-09-15 6:03 ` Julia Lawall [this message]
2016-09-15 6:41 ` Waldemar Rymarkiewicz
2016-09-15 7:44 ` Waldemar Rymarkiewicz
2016-09-15 7:59 ` Julia Lawall
2016-09-15 8:11 ` [Cocci] Match #define with SmPL SF Markus Elfring
2016-09-20 12:38 ` Waldemar Rymarkiewicz
2016-09-20 18:20 ` SF Markus Elfring
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.10.1609150803290.6497@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 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.