All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emese Revfy <re.emese@gmail.com>
To: Julia Lawall <julia@diku.dk>
Cc: Kees Cook <kees.cook@canonical.com>,
	linux-kernel@vger.kernel.org, cocci@diku.dk,
	Lionel Debroux <lionel_debroux@yahoo.fr>,
	Brad Spengler <spender@grsecurity.net>
Subject: Re: [Cocci] Re: status of constification
Date: Sat, 13 Nov 2010 13:13:28 +0100	[thread overview]
Message-ID: <4CDE80E8.6060601@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1011112352030.27612@ask.diku.dk>

>>> What would the right approach be?  It is not obvious to find 100% of the 
>>> header files, because some of them depend on information in Makefiles.  
>>
>> For 100% coverage you can look at how the Linux Makefiles invoke sparse.
> 
> I haven't looked at it, but I doubt it gives 100% coverage, because one 
> can have code in both the if and else branches of an ifdef.  I would 
> imagine that it gives 100% coverage for whatever architecture you would be 
> compiling for?

For my purposes it's enough to find all includes for a given .config.

What would be also useful is if Coccinelle could somehow ignore ifdef's that
guard code blocks so that it would analyse all code in a translation unit. 

Thanks Emese


  reply	other threads:[~2010-11-13 12:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08 22:38 status of constification Kees Cook
2010-11-09 21:54 ` Emese Revfy
     [not found] ` <4CD9BF25.4090306@gmail.com>
2010-11-10  6:35   ` [Cocci] " Julia Lawall
2010-11-11 21:48     ` Emese Revfy
2010-11-11 22:53       ` Julia Lawall
2010-11-13 12:13         ` Emese Revfy [this message]
2010-11-13 13:43           ` Julia Lawall
2010-11-13 14:41       ` Julia Lawall
2011-05-28  3:13   ` Kees Cook
2011-05-28  6:39     ` [Cocci] " Julia Lawall
2011-06-05 21:47       ` Emese Revfy
2011-06-06  5:03         ` Julia Lawall
2011-06-06  7:49         ` Julia Lawall
2011-06-10 21:28           ` Emese Revfy

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=4CDE80E8.6060601@gmail.com \
    --to=re.emese@gmail.com \
    --cc=cocci@diku.dk \
    --cc=julia@diku.dk \
    --cc=kees.cook@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lionel_debroux@yahoo.fr \
    --cc=spender@grsecurity.net \
    /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.