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

Re: [Cocci] git-coccinelle: adjustments for array.cocci?

From
MEMarkus Elfring <markus.elfring@web.de>
Date
Nov 16, 2019, 08:29 UTC
Message-ID
<22a03cac-160b-51be-b015-54ac600d3e92@web.de>
In-Reply-To
<alpine.DEB.2.21.1911152000170.8961@hadrien>
> It can determine the type of t->entries if it has access to the definition
> of the type of t.
I would like to point another implementation detail out.

Another known function was also an update candidate. https://github.com/git/git/blob/9a1180fc304ad9831641e5788e9c8d3dfc10ccdd/pretty.c#L90

elfring@Sonne:~/Projekte/git/lokal> spatch contrib/coccinelle/array.cocci pretty.c …

@@ -106,8 +106,8 @@ static void setup_commit_formats(void)
        commit_formats_len = ARRAY_SIZE(builtin_formats);
        builtin_formats_len = commit_formats_len;
        ALLOC_GROW(commit_formats, commit_formats_len, commit_formats_alloc);
-       memcpy(commit_formats, builtin_formats,
-              sizeof(*builtin_formats)*ARRAY_SIZE(builtin_formats));
+       COPY_ARRAY(commit_formats, builtin_formats,
+                  ARRAY_SIZE(builtin_formats));

        git_config(git_pretty_formats_config, NULL);
 }


This patch generation can work based on the following SmPL code combination.

“…
expression n, x;
…
-      , (n) * \( sizeof(T) \| sizeof(*(x)) \)
…”

The asterisk should refer to a pointer expression within a sizeof operator.
I got informed that the semantic patch language would support such a restriction.

Thus I have tried out to specify the corresponding metavariables in this way.

“…
expression n;
expression* x;
…”

But the shown diff hunk is not regenerated by this SmPL script variant.
How should an array like “builtin_formats” (which is even defined in the same function)
be treated by the Coccinelle software in such use cases?

Regards,
Markus
Previous: Markus ElfringNext: Julia Lawall
Message 15 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.