Coccinelle Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] coccinelle: api: add sprintf() support to device_attr_show
Date: Sat, 5 Sep 2020 09:39:04 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2009050937480.2363@hadrien> (raw)
In-Reply-To: <afbbc6f1-ca60-e780-0139-d944165e456f@web.de>

[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]



On Sat, 5 Sep 2020, Markus Elfring wrote:

> >>> What clarifications?
> >>
> >> Did you notice that my suggestion for the SmPL script variant “scripts/coccinelle/api/device_attr_show.cocci”
> >> can generate a patch?
> >> https://lore.kernel.org/cocci/0a9015b6-9037-59c5-31f2-cd2b32c86b50@linux.com/
> >>
> >> Unfortunately, it seems that this transformation approach produces also
> >> an inappropriate test result so far.
> >> Do we expect that the first part of the SmPL disjunction should match
> >> (for the source file “drivers/base/core.c” for example)?
> >
> > This semantic patch triggers the same problem as the original one,
>
> This view is interesting.
>
>
> > and should benefit from the same solution.
>
> I noticed the commit “improve andany optimization” yesterday.
> https://github.com/coccinelle/coccinelle/commit/1a5502d4be8db0623b5acead974943098bdcbf57
>
> The change description contains the following information.
>
> “…
> It also makes the test failing_andany work, which did not work previously.
> …”
>
> I would hope for further positive consequences. Thus I have tried
> the software “Coccinelle 1.0.8-00168-gc4048513” out again.
> But I observe that the expected patch is still not generated
> if a special SmPL disjunction should be applied in my test case.
> The expected test result is displayed if a source code search
> should be performed according to extracted code from the first branch
> of such a disjunction (so that no disjunction is specified in
> the SmPL script variant).
>
> How will the clarification be continued?

The clarification will be continued when you provide a small semantic
patch and a C file that causes a problem.  I'm not going to hunt in years
of mail archives to find it.  If you want something to happen you have to
provide that information now.

julia

[-- Attachment #2: Type: text/plain, Size: 136 bytes --]

_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  parent reply	other threads:[~2020-09-05  7:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ed9a8046-4c21-e849-f68b-9e08991b701d@web.de>
2020-08-14  8:50 ` [Cocci] [PATCH] coccinelle: api: add sprintf() support to device_attr_show Denis Efremov
     [not found]   ` <48ffa436-6e73-88b2-07bc-89942f3c6d8e@web.de>
2020-08-14 14:36     ` Denis Efremov
     [not found]       ` <047eaa85-20cf-800d-7087-a980f53572de@web.de>
2020-08-16  8:37         ` [Cocci] Searching for format strings with SmPL disjunctions Markus Elfring
2020-08-16  8:43           ` Julia Lawall
2020-08-16  8:48             ` Markus Elfring
2020-08-16 11:00             ` Markus Elfring
2020-08-15 10:32   ` [Cocci] [PATCH] coccinelle: api: add sprintf() support to device_attr_show Julia Lawall
2020-08-17  7:00     ` [Cocci] " Markus Elfring
2020-08-17  7:42       ` Julia Lawall
2020-08-17  7:57         ` Markus Elfring
2020-08-17  8:02           ` Julia Lawall
     [not found]             ` <cad4141c-8cba-3705-a502-0620ae3df027@web.de>
2020-08-17  8:24               ` Julia Lawall
     [not found]                 ` <1e60d36d-7f2b-98eb-5fe3-9729b97ba360@web.de>
2020-08-17 16:29                   ` Julia Lawall
     [not found]                     ` <afbbc6f1-ca60-e780-0139-d944165e456f@web.de>
2020-09-05  7:39                       ` Julia Lawall [this message]
     [not found]                         ` <26349832-57a8-4c6e-efc9-0febd5650922@web.de>
2020-09-05  9:53                           ` Julia Lawall
2020-09-05 11:08                           ` 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.22.394.2009050937480.2363@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=Markus.Elfring@web.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox