This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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

From: kaih at khms dot westfalen dot de (Kai Henningsen)
To: gcc-help at gcc dot gnu dot org
Date: 26 Oct 2005 10:38:00 +0200
Subject: Re: Is there a way to restrict function calls (at compile time)?
References: <1130111348.7258.60.camel@c213-100-50-8.swipnet.se> <1130111348.7258.60.camel@c213-100-50-8.swipnet.se> <435CA8DD.20902@codesourcery.com>

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

Follow-Ups:
- Re: Is there a way to restrict function calls (at compile time)?
  - From: John Love-Jensen
- Re: Is there a way to restrict function calls (at compile time)?
  - From: Lars Luthman

References:
- Is there a way to restrict function calls (at compile time)?
  - From: Lars Luthman
- Re: Is there a way to restrict function calls (at compile time)?
  - From: Nathan Sidwell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]