From: Julia Lawall <julia.lawall@lip6.fr>
To: Nishanth Menon <nm@ti.com>
Cc: Vaishali Thakkar <vaishali.thakkar@oracle.com>,
Michal Marek <mmarek@suse.com>,
linux-next@vger.kernel.org, cocci@systeme.lip6.fr
Subject: Re: [cocci: new build warnings]: next-20160316 setup_timer.cocci
Date: Fri, 18 Mar 2016 11:22:48 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.10.1603181108000.2581@hadrien> (raw)
In-Reply-To: <56E9F4F8.70708@ti.com>
On Wed, 16 Mar 2016, Nishanth Menon wrote:
> Hi,
>
> It looks like commit c5eda8fd10c6 ("Coccinelle: Add
> api/setup_timer.cocci") with spatch rev(1.0.4 latest)[1] generates
> warning [2]. I am using spatch from the latest git tree[3]
>
> rule name: parse error:
> File "./scripts/coccinelle/api/setup_timer.cocci", line 109, column 0,
> charpos = 1939
> around = '(',
> whole content = '(context || org || report)@'
Thanks again for the report. The problem is just the newline before the
(, whch causes the ( to be differently interpreted (for a disjunction).
There is no need for such an interpretation in this position in the code,
so I have updated Coccinelle. The update should be in github by the end
of the day.
Probably we should submit a patch on the semantic patch to add a space in
front of the offending parentheses, to make the rule usable with all
versions.
julia
>
> [1]
> spatch byte-code version 1.0.4-00203-gdb45d7549bdd compiled with OCaml
> version 4.01.0
> Flags passed to the configure script: [none]
> Python scripting support: yes
> Syntax of regular expresssions: PCRE
>
> [2] http://pastebin.ubuntu.com/15405226/
> [3] https://github.com/coccinelle/coccinelle.git
>
> --
> Regards,
> Nishanth Menon
>
prev parent reply other threads:[~2016-03-18 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 0:06 [cocci: new build warnings]: next-20160316 setup_timer.cocci Nishanth Menon
2016-03-17 5:33 ` Julia Lawall
2016-03-18 10:22 ` Julia Lawall [this message]
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.1603181108000.2581@hadrien \
--to=julia.lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=nm@ti.com \
--cc=vaishali.thakkar@oracle.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