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 17:00:51 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.2001151700090.5079@hadrien> (raw)
In-Reply-To: <20200115155902.GA8632@redhat.com>
On Wed, 15 Jan 2020, Oleg Nesterov wrote:
> On 01/15, Julia Lawall wrote:
> >
> > On Wed, 15 Jan 2020, Oleg Nesterov wrote:
> >
> > > $ 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.
>
> Yes, thanks, this was clear to me,
>
> > You can disable the file
> > filtering with --disable-worth-trying-opt.
>
> Heh. I swear, I even did
>
> $ spatch --longhelp 2>&1 | grep disable
>
> but apparently I can't read.
The name is not super intuitive, and is more tied to the code than the
user intuition. I spent some time searching for -no- and for something
about files.
julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-01-15 16:01 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
2020-01-15 15:59 ` Oleg Nesterov
2020-01-15 16:00 ` Julia Lawall [this message]
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.2001151700090.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).