Coccinelle Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Parsing C source files by Coccinelle
Date: Tue, 8 Mar 2016 11:26:29 +0100	[thread overview]
Message-ID: <56DEA8D5.6070902@users.sourceforge.net> (raw)
In-Reply-To: <CAGbDTvr_nmt-SVtvYtvOM9tcsUvh_tdg0i=+R1QDLck0G9uctg@mail.gmail.com>

> If you are talking about using Coccinelle as a bug finder,
> and empower it with alias analysis,

I am also curious on how such technologies will fit together.


> then I have spent about a year working on a similar idea.

How similar was this approach?


> I am available to discuss my experience with you,

Nice ?


> if you want.

Yes, please.


> I don't know exactly in what direction you want to "improve" Coccinelle results,
> but let me warn you that in principle alias analysis may just give you
> a lot more false positives.

Do you need also a special software infrastructure to reduce the probability
for the undesired reporting of false positives?


> Sometimes, in functions with complex manipulation of pointers,
> I find that alias analysis hurts more than it helps.

Interesting view ?


> That said, I think advanced Coccinelle users could make good use
> of aliasing information.

How would these data be integrated for the use in SmPL scripts?

Regards,
Markus

  reply	other threads:[~2016-03-08 10:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  0:43 [Cocci] Coccinelle Compilation Problem: configure file Aftab Hussain
2016-03-04  7:09 ` Julia Lawall
2016-03-07 15:54   ` Aftab Hussain
2016-03-08  8:57     ` Sébastien Hinderer
2016-03-04 14:32 ` [Cocci] Regeneration of the script "configure" for Coccinelle SF Markus Elfring
     [not found]   ` <CAO=9Y+2Qm+A9a91zGrYNJavOXcWFR2hj5Xx+=FPG1p02KdC7Ew@mail.gmail.com>
2016-03-07 18:39     ` [Cocci] Parsing C source files by Coccinelle SF Markus Elfring
     [not found]       ` <CAO=9Y+0KUsrK4OpR9YrNpp5JJ2tDDoY-DOq0xfDBcY8GdKWwCQ@mail.gmail.com>
2016-03-07 19:55         ` SF Markus Elfring
2016-03-08  9:59           ` Iago Abal
2016-03-08 10:26             ` SF Markus Elfring [this message]
2016-03-08 12:01               ` Iago Abal
2016-03-08 13:50                 ` SF Markus Elfring
2016-03-09 13:42                   ` Iago Abal
2016-03-09 16:34                     ` SF Markus Elfring
2016-03-10  1:02                     ` Julia Lawall
2016-03-07 21:57       ` Julia Lawall
2016-03-07 22:20         ` SF Markus Elfring
2016-03-07 22:29           ` Julia Lawall
2016-03-08  9:01             ` SF Markus Elfring
2016-03-08 10:55               ` Julia Lawall
2016-03-08 11:43                 ` [Cocci] Checking build parameters for Menhir SF Markus Elfring
2016-03-08  9:00       ` [Cocci] Parsing C source files by Coccinelle Sébastien Hinderer
2016-03-08  9:20         ` SF Markus Elfring
2016-03-08  9:25           ` Sébastien Hinderer
2016-03-08  9:33             ` SF 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=56DEA8D5.6070902@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --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