From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: cocci@systeme.lip6.fr
Subject: [Cocci] Does coccinelle support non-standard C?
Date: Wed, 22 May 2019 13:28:51 +0200 [thread overview]
Message-ID: <86fdc128-e077-58d1-2170-912937317ab1@linbit.com> (raw)
Hi,
Consider the following snippet of C:
#define f() ({ puts("hello"); 0; })
int main()
{
printf("%d\n", f());
}
It uses an expression statement in the definition of `f`, which is a gcc
extension.
Now let's try to write a semantic patch to generate something like this:
@@
@@
- cocci_replace_this()
+ ({ puts("hello"); 0; })
With the C code as:
#define f() cocci_replace_this()
int main()
{
printf("%d\n", f());
}
This prompts the following error message from spatch:
$ spatch --sp-file test.cocci test.c
init_defs_builtins: /usr/lib/coccinelle/standard.h
32 33
Fatal error: exception Failure("plus: parse error: \n = File
\"test.cocci\", line 4, column 3, charpos = 32\n around = '{', whole
content = + ({ puts(\"hello\"); 0; })\n")
Now here's my question: this obviously implies that coccinelle doesn't
support expression statements (or any other non-standard C for that
matter). Can I still somehow tell spatch to just replace it with this
string of text instead of trying to parse it as C?
Thanks.
--
Regards,
Christoph
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next reply other threads:[~2019-05-22 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 11:28 Christoph Böhmwalder [this message]
2019-05-22 11:37 ` [Cocci] Does coccinelle support non-standard C? Julia Lawall
2019-05-22 11:39 ` Christoph Böhmwalder
2019-05-22 11:55 ` Julia Lawall
2019-05-22 11:57 ` Christoph Böhmwalder
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=86fdc128-e077-58d1-2170-912937317ab1@linbit.com \
--to=christoph.boehmwalder@linbit.com \
--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.