git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: coccinelle: improve array.cocci

From
MEMarkus Elfring <markus.elfring@web.de>
Date
Nov 21, 2019, 19:44 UTC
Message-ID
<06ff24b6-f154-9ec6-7b22-05b0ea664a36@web.de>
In-Reply-To
<4f55b06b-35f3-da06-ae86-8a4068f78027@web.de>
>> This case distinction can share a few metavariables with the other
>> transformation approach, can't it?
>
> Can it can, but should it?  In my opinion it should not;

I presented a software design in an other direction. Some data processing approaches can benefit from sharing common information.

> separate concerns should get their own rules.
Strict separation triggers corresponding consequences.
> That's easier to manage for developers.
This view can be reasonable.
> I suspect it's also easier for Coccinelle to evaluate, but didn't check.
I find such an assumption questionable.
> I use MAKEFLAGS += -j6, which runs six spatch instances in
> parallel for the coccicheck make target of Git instead.

The program “spatch” supports parallelisation also directly by the parameter “--jobs”. Did you try it out occasionally?

> OK, so --profile allows to analyze in which of its parts Coccinelle
> spends the extra time.
Some information about time distribution will be displayed.
>> I suggest to use a search for (pointer) expressions instead.
>> This approach can trigger other consequences then.
>
> Why don't we need to check the type?

I got the impression that we stumble on a general challenge for generic source code searches. How many efforts would we like to invest in solving type safety issues?

>> Would you eventually work with SmPL script variants in parallel according
>> to different confidence settings?
>
> Me?  No.
Such a view can be fine.

But I am also still trying to improve various implementation details despite of known software limitations.

> If I can't trust automatic transformations then I don't want them.
I need to live with compromises together also with current development tools.
> I can already generate bugs fast enough manually, thank you very much. :)
This is usual.
I hope that specific tools can make our lives occasionally a bit easier.

Regards, Markus

Previous: René ScharfeNext: SZEDER Gábor
Message 36 of 41 in “coccinelle: adjustments for array.cocci?”
  1. Markus ElfringNov 12, 2019
  2. René ScharfeNov 12, 2019
  3. Junio C HamanoNov 13, 2019
  4. Markus ElfringNov 13, 2019
  5. Junio C HamanoNov 14, 2019
  6. Markus ElfringNov 14, 2019
  7. René ScharfeNov 14, 2019
  8. Markus ElfringNov 14, 2019
  9. René ScharfeNov 14, 2019
  10. Markus ElfringNov 15, 2019
  11. Markus ElfringNov 15, 2019
  12. Markus ElfringNov 15, 2019
  13. Julia LawallNov 16, 2019
  14. Markus ElfringNov 16, 2019
  15. Markus ElfringNov 16, 2019
  16. Julia LawallNov 16, 2019
  17. Markus ElfringNov 16, 2019
  18. Markus ElfringNov 15, 2019
  19. René ScharfeNov 16, 2019
  20. Markus ElfringNov 17, 2019
  21. René ScharfeNov 17, 2019
  22. Markus ElfringNov 17, 2019
  23. René ScharfeNov 19, 2019
  24. Markus ElfringNov 19, 2019
  25. René ScharfeNov 21, 2019
  26. Markus ElfringNov 16, 2019
  27. René ScharfeNov 16, 2019
  28. Markus ElfringNov 17, 2019
  29. René ScharfeNov 17, 2019
  30. Markus ElfringNov 17, 2019
  31. René ScharfeNov 19, 2019
  32. coccinelle: improve array.cocciMarkus Elfring, Nov 18, 2019
  33. René ScharfeNov 19, 2019
  34. Markus ElfringNov 20, 2019
  35. René ScharfeNov 21, 2019
  36. Markus ElfringNov 21, 2019
  37. SZEDER GáborNov 22, 2019
  38. Markus ElfringNov 22, 2019
  39. Junio C HamanoNov 22, 2019
  40. Markus ElfringNov 22, 2019
  41. Markus ElfringJan 25, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.