[splint-discuss] empedded programming, __interrupt (plain txt, no html, sorry)

[Matuschka, Sebastian]

Sorry i forgot to change to "only text", here is the mail in plain text,
no html

Hello,
 
i want to use splint for analysis on c code for empedded systems.
The compiler (i.e. FUJITSU) for embedded code accepts some additional
things like "__interrupt" for defining a function as an interrupt. As of
the nature of an interrupt this function gets never called in the code.
But i do want splint to check if other functions which are no interrupts
are used. And here is the problem. When i call splint with the option
-D__interrupt=const i get no warnings because __interrupt is unknown to
splint, but splint warns because the interrupt function is unused. So
how can i tell splint that all functions which look like
__interrupt void intIOTimer (void)
{
...
}
are not called in my program and therefor it isn't neccessary to warn
that they are unused.
I don't want to write %@unused@% in front of every interrupt, i want
that splint knows this because of the __interrupt.
I have compiled splint 3.1.2 on windows and made some little changes on
the code, so i know a bit about the splint sources and how splint works.
But it is a bit too much for me to change the bison and lex parser and
these arrays full of numbers like yytoknum, yyr1 and so on so it knows
__interrupt for example.
I am thankful for every idea or hint how to solve this problem.
 
Greetings
Sebastian Matuschka