mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter T. Breuer" <ptb@inv.it.uc3m.es>
To: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: .o.cmd files wanted, static analysis
Date: Fri, 16 Sep 2005 01:50:29 +0200 (MET DST)	[thread overview]
Message-ID: <200509152350.j8FNoTM17346@inv.it.uc3m.es> (raw)

(was sent to Linux Testing Project list, but no answer there yet).


G'day all

I'm looking for a set of .*.o.cmd files for the 2.6 kernel. These are
generated when you compile the kernel. I have about 1600 of them from my
standard compilation choices, but I want the full 6000 odd so that I can
run static analysis tests.

See ftp://oboe.it.uc3m.es/pub/Programs/c-1.2.*.tgz

The currently enabled tests are for sleep under spinlock, double spinlock,
and access to kfree'd memory. I'll add more according to suggestions
received. About 3 errors in each class are detected for every 1000
kernel source files, with about three times that many false alarms
raised. It takes a few seconds per file, at about 10000 expanded lines
of code per second.

Does somebody out there have a pretty complete kernel compilation,
mainly all modules (though I don't care!), and could let me have their
 .*.o.cmd files? In fact, just the FIRST LINE of them.
 
That first line gives me the compile flags used.

Thanks.

Peter



             reply	other threads:[~2005-09-15 23:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15 23:50 Peter T. Breuer [this message]
2005-09-16  0:08 ` Kyle Moffett
2005-09-16  6:46   ` Peter T. Breuer
     [not found] <200509161502.17861.lion.vollnhals@web.de>
2005-09-16 18:39 ` Peter T. Breuer
     [not found] <432B332F.8070808@tuxrocks.com>
2005-09-17  4:25 ` Peter T. Breuer

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=200509152350.j8FNoTM17346@inv.it.uc3m.es \
    --to=ptb@inv.it.uc3m.es \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®