From: Julia Lawall <julia.lawall@inria.fr>
To: Oleg Nesterov <oleg@redhat.com>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] Q: does spatch understand typeof?
Date: Wed, 15 Jan 2020 16:45:32 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.2001151641200.5079@hadrien> (raw)
In-Reply-To: <20200115153035.GA9172@redhat.com>
On Wed, 15 Jan 2020, Oleg Nesterov wrote:
> On 01/15, Julia Lawall wrote:
> >
> > Yes, it doesn't currently understand typeof. If it's a big problem, it
> > should be easy to fix.
>
> OK, thanks Julia.
>
> Another question...
>
> inc.h:
>
> struct TTT { int mem; } *ptr;
>
> test.c:
>
> #include "inc.h"
>
> void func(void)
> {
> ptr->mem = 0;
> }
>
> test.cocci:
>
> @r@
> struct TTT *p;
> @@
>
> * p->mem
>
> $ spatch --sp-file test.cocci test.c
>
> (ONCE) Expected tokens mem TTT
> Skipping: test.c
>
> I tried to play with various --.*include.* options, but nothing seems to work
> unless I add "inc.h" to the command line explicitly.
The problem is that the file filtering happens before the parsing, and it
is the parsing that finds the includes. You can disable the file
filtering with --disable-worth-trying-opt.
julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-01-15 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 11:25 [Cocci] Q: does spatch understand typeof? Oleg Nesterov
2020-01-15 12:09 ` Julia Lawall
2020-01-15 15:30 ` Oleg Nesterov
2020-01-15 15:45 ` Julia Lawall [this message]
2020-01-15 15:59 ` Oleg Nesterov
2020-01-15 16:00 ` Julia Lawall
2020-01-15 15:53 ` Oleg Nesterov
2020-01-15 15:59 ` Julia Lawall
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.21.2001151641200.5079@hadrien \
--to=julia.lawall@inria.fr \
--cc=cocci@systeme.lip6.fr \
--cc=oleg@redhat.com \
/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 NNTP newsgroup(s).