All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Searching for pass-through functions
Date: Sat, 04 Oct 2014 19:49:52 +0200	[thread overview]
Message-ID: <54303340.3090901@users.sourceforge.net> (raw)

Hello,

I have retried a source code analysis approach which was discussed a while ago.
http://article.gmane.org/gmane.comp.version-control.coccinelle/1900
https://www.mail-archive.com/cocci%40diku.dk/msg01834.html


elfring at Sonne:~/Projekte/Coccinelle/lokal/demos/pass-through> spatch.opt
-sp_file list_pass-through_functions.cocci -dir /usr/src/linux-stable
--include-headers-for-types >list_pass-through_functions-Linux-3_16_3.txt
2>list_pass-through_functions-Linux-3_16_3-errors.txt


I have stopped this run after its execution took over 4,8 hours with the
software "Coccinelle 1.0.0-rc22" on my openSUSE system. A log file contains the
following information.

?
HANDLING: /usr/src/linux-stable/drivers/media/pci/ttpci/av7110_ipack.c
     C-c intercepted, will do some cleaning before exiting


Can it be that the analysis tool became stuck on this source file after 4054
files were processed before?

How are the chances to complete the desired data extraction for all 23753 C
files in a shorter time frame?

Regards,
Markus

             reply	other threads:[~2014-10-04 17:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-04 17:49 SF Markus Elfring [this message]
2014-10-04 19:17 ` [Cocci] Searching for pass-through functions Julia Lawall
2014-10-04 20:22   ` SF Markus Elfring
2014-10-04 21:32     ` Julia Lawall
2014-10-05  6:48       ` SF Markus Elfring
2014-10-05  9:39         ` Julia Lawall
2014-10-05 13:15           ` SF Markus Elfring
2014-10-05 11:45       ` SF Markus Elfring
2014-10-05 11:48         ` Julia Lawall
2014-10-05 12:15           ` SF Markus Elfring
2014-10-05 15:33             ` Julia Lawall
2014-10-05 16:38               ` SF Markus Elfring
2014-10-05 16:42                 ` Julia Lawall
2014-10-05 16:55                   ` SF Markus Elfring
2014-10-05 17:01                     ` Julia Lawall
2014-10-05 17:09                       ` SF Markus Elfring
2014-10-05 18:37               ` SF Markus Elfring
2014-10-08 11:40               ` SF Markus Elfring
2014-10-08 11:51                 ` Julia Lawall
2014-10-08 12:01                   ` SF Markus Elfring
2014-10-08 12:08                     ` Julia Lawall
2014-10-08 12:20                       ` SF Markus Elfring
2014-10-08 12:48                         ` Julia Lawall
2014-10-08 13:01                           ` SF Markus Elfring
2014-10-08 18:05                           ` SF Markus Elfring
2014-10-09  5:37                             ` Julia Lawall
2014-10-07 19:39 ` SF Markus Elfring
2014-10-07 19:44   ` Julia Lawall
2014-10-07 20:20     ` SF Markus Elfring
2014-10-07 20:26       ` 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=54303340.3090901@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.