Is there a way to restrict function calls (at compile time)?

Is there a way to restrict function calls (at compile time)?

[Lars Luthman]

[-- Attachment #1: Type: text/plain, Size: 574 bytes --]

Is there a way, using GCC, to add 'properties' or 'flags' to C and C++
functions and generate warnings or error messages when a function with a
certain property (for example 'realtime safe') tries to call a function
that does not have that property?

I realise that this would be tricky to do for function pointers and
virtual functions, but a solution that only works for 'normal' function
calls will be very useful anyway.

-- 
Lars Luthman
PGP key:     http://www.d.kth.se/~d00-llu/pgp_key.php
Fingerprint: FCA7 C790 19B9 322D EB7A  E1B3 4371 4650 04C7 7E2E

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Is there a way to restrict function calls (at compile time)?

[Nathan Sidwell]

Lars Luthman wrote:
> Is there a way, using GCC, to add 'properties' or 'flags' to C and C++
> functions and generate warnings or error messages when a function with a
> certain property (for example 'realtime safe') tries to call a function
> that does not have that property?

GCC does not have such a feature.

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk

Re: Is there a way to restrict function calls (at compile time)?

[Kai Henningsen]

nathan@codesourcery.com (Nathan Sidwell)  wrote on 24.10.05 in <435CA8DD.20902@codesourcery.com>:

> Lars Luthman wrote:
> > Is there a way, using GCC, to add 'properties' or 'flags' to C and C++
> > functions and generate warnings or error messages when a function with a
> > certain property (for example 'realtime safe') tries to call a function
> > that does not have that property?
>
> GCC does not have such a feature.

Hmm. Can "sparse" do that? I know it can follow data structures in  
different memory spaces ...

(That's the tool Linus wrote to check Linux kernel sources.)

MfG Kai

Re: Is there a way to restrict function calls (at compile time)?

[John Love-Jensen]

Hi everyone,

Kai mentioned "sparse", more info here...
http://www.linuxjournal.com/article/7272

--Eljay

Re: Is there a way to restrict function calls (at compile time)?

[Lars Luthman]

[-- Attachment #1: Type: text/plain, Size: 984 bytes --]

On Wed, 2005-10-26 at 10:38 +0200, Kai Henningsen wrote:
> nathan@codesourcery.com (Nathan Sidwell)  wrote on 24.10.05 in <435CA8DD.20902@codesourcery.com>:
> 
> > Lars Luthman wrote:
> > > Is there a way, using GCC, to add 'properties' or 'flags' to C and C++
> > > functions and generate warnings or error messages when a function with a
> > > certain property (for example 'realtime safe') tries to call a function
> > > that does not have that property?
> >
> > GCC does not have such a feature.
> 
> Hmm. Can "sparse" do that? I know it can follow data structures in  
> different memory spaces ...
> 
> (That's the tool Linus wrote to check Linux kernel sources.)

sparse looks very interesting, especially the context checking.
Unfortunately it seems to be for C only and I need something that works
for C++ as well.

-- 
Lars Luthman
PGP key:     http://www.d.kth.se/~d00-llu/pgp_key.php
Fingerprint: FCA7 C790 19B9 322D EB7A  E1B3 4371 4650 04C7 7E2E

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]