From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Improvements for source code analysis with inclusion of header files
Date: Sun, 30 Mar 2014 13:30:23 +0200 [thread overview]
Message-ID: <5338004F.3090303@users.sourceforge.net> (raw)
Hello,
Some filter patterns can be specified in the semantic patch language so that
they will also work without inclusion of header files. Some other source code
analysis approaches will need all relevant data (e. g. macros and type
declarations) from them.
Various compilers provide a functionality to store processed information from
such headers in an alternative data format.
http://en.wikipedia.org/wiki/Precompiled_header
Would another intermediate form help to reduce analysis and transformation time
by the Coccinelle software here?
How do you think about to store the results from a step "precompilation" like
corresponding abstract syntax graphs in a kind of dedicated data base?
http://en.wikipedia.org/wiki/Graph_database#Graph_database_projects
Regards,
Markus
next reply other threads:[~2014-03-30 11:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 11:30 SF Markus Elfring [this message]
2014-03-30 11:56 ` [Cocci] Improvements for source code analysis with inclusion of header files Julia Lawall
2014-03-30 12:13 ` SF Markus Elfring
2014-03-30 12:26 ` Julia Lawall
2014-03-30 12:33 ` SF Markus Elfring
2014-03-30 12:36 ` Julia Lawall
2014-03-30 12:44 ` SF Markus Elfring
2014-03-30 12:49 ` Julia Lawall
2014-03-30 13:08 ` SF Markus Elfring
2014-03-30 12:45 ` Derek M Jones
2014-03-30 13:00 ` 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=5338004F.3090303@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.