public inbox for cocci@systeme.lip6.fr
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Cc: "Derek M. Jones" <derek@knosof.co.uk>,
	Victor Gambier <victor.gambier@inria.fr>
Subject: Re: [cocci] Broken code block size determination in function implementations
Date: Sun, 27 Oct 2024 18:45:07 +0100	[thread overview]
Message-ID: <f63293b2-94a8-4c2e-933c-5b2f94f64bb2@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2410271833310.3498@hadrien>

> Coccinelle doesn't report on parse errors unless an option like
> --verbose-parsing or --parse-c is provided.

How helpful do you find the following information then?


Markus_Elfring@Sonne:…/Projekte/Linux/next-analyses> spatch --verbose-parsing …/Projekte/Coccinelle/janitor/list_curly_bracket_positions_for_function_implementations4.cocci arch/sh/drivers/pci/common.c
…
HANDLING: arch/sh/drivers/pci/common.c
ERROR-RECOV: found sync col 0 at line 49
parsing pass2: try again
ERROR-RECOV: found sync col 0 at line 49
parsing pass3: try again
Warning: PARSING: arch/sh/drivers/pci/common.c:34: two or more data types: dropping int
, keeping typeD __init

; value = ([0], [0], [(0, 0, (Tag9 ((["__init"; (Tag2 (("__init", 736, 34, 4, "arch/sh/drivers/pci/common.c"), (("\n", 983, 41, 0, "arch/sh/drivers/pci/common.c"), 4)), (0), ((0, 0, 0, 0)), 0, (3))]), 0)))], [(0, 0, 0)], [0])
Warning: PARSING: arch/sh/drivers/pci/common.c:34: two or more data types: dropping int
, keeping typeD __init

; value = ([0], [0], [(0, 0, (Tag9 ((["__init"; (Tag2 (("__init", 736, 34, 4, "arch/sh/drivers/pci/common.c"), (("\n", 1014, 42, 30, "arch/sh/drivers/pci/common.c"), 4)), (0), ((0, 0, 0, 0)), 0, (3))]), 0)))], [(0, 0, 0)], [0])
Warning: PARSING: arch/sh/drivers/pci/common.c:34: two or more data types: dropping int
, keeping typeD __init

; value = ([0], [0], [(0, 0, (Tag9 ((["__init"; (Tag2 (("__init", 736, 34, 4, "arch/sh/drivers/pci/common.c"), (("\n", 1046, 43, 31, "arch/sh/drivers/pci/common.c"), 4)), (0), ((0, 0, 0, 0)), 0, (3))]), 0)))], [(0, 0, 0)], [0])
Warning: PARSING: arch/sh/drivers/pci/common.c:34: two or more data types: dropping int
, keeping typeD __init

; value = ([0], [0], [(0, 0, (Tag9 ((["__init"; (Tag2 (("__init", 736, 34, 4, "arch/sh/drivers/pci/common.c"), (("\n", 1079, 44, 32, "arch/sh/drivers/pci/common.c"), 4)), (0), ((0, 0, 0, 0)), 0, (3))]), 0)))], [(0, 0, 0)], [0])
Warning: PARSING: arch/sh/drivers/pci/common.c:34: two or more data types: dropping int
, keeping typeD __init

; value = ([0], [0], [(0, 0, (Tag9 ((["__init"; (Tag2 (("__init", 736, 34, 4, "arch/sh/drivers/pci/common.c"), (("\n", 1109, 45, 29, "arch/sh/drivers/pci/common.c"), 4)), (0), ((0, 0, 0, 0)), 0, (3))]), 0)))], [(0, 0, 0)], [0])
Warning: PARSING: arch/sh/drivers/pci/common.c:34: two or more data types: dropping int
, keeping typeD __init

; value = ([0], [0], [(0, 0, (Tag9 ((["__init"; (Tag2 (("__init", 736, 34, 4, "arch/sh/drivers/pci/common.c"), (("\n", 1140, 46, 30, "arch/sh/drivers/pci/common.c"), 4)), (0), ((0, 0, 0, 0)), 0, (3))]), 0)))], [(0, 0, 0)], [0])
-> duplicate data
file:
arch/sh/drivers/pci/common.c
function:
early_read_config_dword
line:
36
…



Markus_Elfring@Sonne:…/Projekte/Linux/next-analyses> spatch --parse-c arch/sh/drivers/pci/common.c
…
NB total files = 1; perfect = 1; pbs = 0; timeout = 0; =========> 100%
nb good = 159,  nb passed = 6 =========> 3.64% passed
nb good = 159,  nb bad = 0 =========> 100.00% good or passed


Regards,
Markus

  reply	other threads:[~2024-10-27 17:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 11:56 [cocci] Multiple returns significant performance impact Derek M Jones
2024-10-24 12:42 ` Markus Elfring
2024-10-24 14:48 ` Julia Lawall
2024-10-24 15:23   ` Derek M Jones
2024-10-24 15:29     ` Julia Lawall
2024-10-24 15:35       ` Derek M Jones
2024-10-24 15:38         ` Julia Lawall
2024-10-24 15:44           ` Victor Gambier
2024-10-24 16:00             ` Julia Lawall
2024-10-24 15:50           ` Derek M Jones
2024-10-24 16:07             ` Markus Elfring
2024-10-24 16:14               ` Julia Lawall
2024-10-24 16:48             ` Markus Elfring
2024-10-24 17:30             ` Derek M Jones
2024-10-24 18:26               ` Markus Elfring
2024-10-24 21:03                 ` Derek M Jones
2024-10-25  5:38                   ` Markus Elfring
2024-10-25 11:54                     ` Derek M Jones
2024-10-27 12:48                     ` [cocci] Broken code block size determination in function implementations Markus Elfring
2024-10-27 13:31                       ` Julia Lawall
2024-10-27 15:15                         ` Markus Elfring
2024-10-27 16:40                         ` Markus Elfring
2024-10-27 17:05                           ` Julia Lawall
2024-10-27 17:28                             ` Markus Elfring
2024-10-27 17:34                               ` Julia Lawall
2024-10-27 17:45                                 ` Markus Elfring [this message]
2024-10-27 17:55                                   ` Julia Lawall
2024-10-27 18:04                                     ` Markus Elfring
2024-10-27 18:00                                   ` Derek M Jones
2024-10-27 18:11                                     ` [cocci] Evolving experiences from evidence-based software engineering Markus Elfring
2024-10-28  9:00                               ` [cocci] Searching for macro calls besides function implementations (with SmPL)? Markus Elfring
2024-10-28 12:57                                 ` Julia Lawall
2024-10-28 10:44                             ` [cocci] Broken code block size determination in function implementations Markus Elfring
2024-10-29 12:17                             ` Markus Elfring
2024-10-31  7:50                             ` Markus Elfring
2024-10-26 11:43             ` [cocci] Checking SmPL run time characteristics for code block position " Markus Elfring
2024-10-24 16:16           ` [cocci] SmPL position variables … Markus Elfring
2024-10-24 16:20             ` Julia Lawall
2024-10-24 16:28               ` Markus Elfring

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=f63293b2-94a8-4c2e-933c-5b2f94f64bb2@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@inria.fr \
    --cc=derek@knosof.co.uk \
    --cc=julia.lawall@inria.fr \
    --cc=victor.gambier@inria.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